Bug 35302 - Problem rendering storybord
Summary: Problem rendering storybord
Status: RESOLVED ANSWERED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 3.11 (C5)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-10-27 14:12 UTC by Mathieu RENE
Modified: 2015-11-02 11:05 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
iOS designer log (6.28 KB, application/octet-stream)
2015-10-27 14:13 UTC, Mathieu RENE
Details
visual studio xamarin log (10.83 KB, application/octet-stream)
2015-10-27 14:13 UTC, Mathieu RENE
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description Mathieu RENE 2015-10-27 14:12:33 UTC
i can't edit any storybord file in visual studio. after 10 min loading i have this error message "there was a problem rendering this document"

thanks
Comment 1 Mathieu RENE 2015-10-27 14:13:15 UTC
Created attachment 13547 [details]
iOS designer log
Comment 2 Mathieu RENE 2015-10-27 14:13:37 UTC
Created attachment 13548 [details]
visual studio xamarin log
Comment 3 Alan McGovern 2015-11-02 11:05:54 UTC
We've fixed many cases of this in the 4.x series. Your best bet is to just update to the new Release Candidate. If the issue is not already fixed there we will the logs from the new version to diagnose the issue.