Bug 20905 - Aspect ratio constraint causes 'There was a problem rendering this document'
Summary: Aspect ratio constraint causes 'There was a problem rendering this document'
Status: RESOLVED DUPLICATE of bug 21424
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 3.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-06-26 10:53 UTC by Sam
Modified: 2014-07-26 14:51 UTC (History)
5 users (show)

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

Stack trace from Visual Studio iOS Designer (3.78 KB, text/plain)
2014-06-26 10:53 UTC, Sam
Stack trace from Xamarin Studio (249.67 KB, text/plain)
2014-06-26 10:54 UTC, Sam

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:

Description Sam 2014-06-26 10:53:44 UTC
Created attachment 7197 [details]
Stack trace from Visual Studio iOS Designer

I get a 'There was a problem rendering this document' error when attempting to open a Storyboard that has had an Aspect Ratio constraint added to a view via XCode.

Because of this, Storyboards designed using XCode cannot be opened in the Xamarin iOS Interface designer if those storyboards contain Aspect Ratio constraints.

This problem appears to affect both Xamarin Studio and Visual Studio.

Steps to reproduce:
Create new iOS storyboard project in Xamarin Studio / Visual Studio
Add UIImageView to main View
Open Storyboard with XCode
Add Aspect Ratio Constraint to UIImageView
Reopen in Xamarin Studio/Visual Studio

I've attached a stack trace for the error as it appears in Visual Studio.

Comment 1 Sam 2014-06-26 10:54:35 UTC
Created attachment 7198 [details]
Stack trace from Xamarin Studio
Comment 2 Parmendra Kumar 2014-07-21 11:41:05 UTC
I have checked this issue with following steps as mentioned below and able to reproduce this issue. 
1. Create a storyboard project in Xamarin Studio.
2. Add control ImageView to storyboard.
3. Close the storyboard.
3. Right click on storyboard and open it with Xcode.
4. Add aspect ratio Constraint to ImageView and Save it.
5. Now reopen storyboard.

Log: https://gist.github.com/Parmendrak/7d314907df2ae3124f33

ScreenCast: http://www.screencast.com/t/QaSFfQ5v

=== Xamarin Studio ===

Version 5.1.4 (build 0)
Installation UUID: 67eaf3b4-f8a7-4ab4-a9df-3197350ca5dc
	Mono 3.4.0 ((no/c3fc3ba)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 304000204

=== Xamarin.Android ===

Version: 4.12.6
Android SDK: Not found

=== Apple Developer Tools ===

Xcode 5.1.1 (5085)
Build 5B1008

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 87026b6
Build date: 2014-07-02 19:39:08-0400

=== Xamarin.Mac ===


=== Build Information ===

Release ID: 501040000
Git revision: 7d45bbe2ee22625f125d0c52548524f02d005cca
Build date: 2014-07-14 12:15:53-04
Xamarin addins: c78f1d88e57baa928aeee1484d96e6f8edf8de33

=== Operating System ===

Mac OS X 10.9.4
Darwin Ixamarin78s-iMac.local 13.3.0 Darwin Kernel Version 13.3.0
    Tue Jun  3 21:27:35 PDT 2014
    root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
Comment 3 Alan McGovern 2014-07-26 14:51:33 UTC
I believe this is a duplicate of bug 21424. If this is not the case, please re-open the bug and attach a sample of the storyboard which triggers the error. Thanks!

*** This bug has been marked as a duplicate of bug 21424 ***