Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 or GitHub 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.
Description of Problem:
PageViewController Transition Styles are not reflected correctly between iOS Designer and Interface Builder. They are the opposite of the (correct) transition style shown in interface builder
Steps to reproduce the problem:
1. Create a Page View Controller in iOS Designer and close.
2. In Interface Builder change transition style from Curl to Scroll
3. View Transition Style in iOS Designer
Page Curl in iOS Designer shows as Scroll, and vice versa
Transitional Styles should be correctly mapped
How often does this happen?
iOS Indie License
Jeremie, when we select 'curl' we end up writing '1' to the xml. I think this is causing the issue they're seeing.
This should be backported as we are corrupting the xml.
Fixed the initial XML issue, but I have noticed a slew of problem on the server side which all seem to boil down to UIPageViewController thinking that the placeholder view we are using is a valid delegate or something.
That generates a lot of native error like:
-[MonoTouch.Design.PlaceholderView invalidatePageViewController]: unrecognized selector sent to instance 0x146c5ab0
I fixed the aspect of it now.
I have verified this by creating a small iOS application with page view controller. I followed the same steps mentioned in description and see following results.
1. Add PageViewController in MainStoryboard. By default property of Transition Style is' Page Curl'.
2. Close MainStoryboard page.
3. Right click on MainStoryboard page > Open With > Xcode Interface Builder.
4. Change the of Transition Style into 'Scroll'.
5. Now Open MainStoryboard page in iOS designer, see the Transition Style it is appearing as 'Scroll'.
6. Repeat step 2 and 3.
7. Change the of Transition Style into 'Page Curl'.
8. Now Open MainStoryboard page in iOS designer, see the Transition Style it is appearing as 'Page Curl'.
Screen Cast for the same :
Environment Info :
=== Xamarin Studio ===
Version 4.2.4 (build 266)
Installation UUID: ce3f5199-e126-42fd-bc8a-6a96370af9ab
Mono 3.2.6 ((no/9b58377)
GTK+ 2.24.23 (Raleigh theme)
Package version: 302060000
=== Xamarin.Android ===
Version: 4.13.0 (Trial Edition)
Android SDK: /Users/mac109/Desktop/android-sdk-macosx
Supported Android versions:
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.4 (API level 19)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
=== Apple Developer Tools ===
Xcode 5.0 (3332.22)
=== Xamarin.iOS ===
Version: 220.127.116.11 (Trial Edition)
Build date: 2014-10-03 18:02:26-0400
=== Xamarin.Mac ===
Xamarin.Mac: Not Installed
=== Build Information ===
Release ID: 402040266
Git revision: 57fa6b7639703775ae1d5c46536e42ab424cb177
Build date: 2014-03-20 12:34:27-04
Xamarin addins: eee141c29724a19529e77b8e743086d95b29f5ba
=== Operating System ===
Mac OS X 10.9.2
Darwin mac109s-Mac-mini.local 13.1.0 Darwin Kernel Version 13.1.0
Thu Jan 16 19:40:37 PST 2014
Hence, Marked this fix as verified.
Shruti, your environment build paste suggests you're testing with an earlier version of Xamarin Studio and Xamarin.iOS than the one this bug was reported with. Am I just reading into that wrong and the fix was actually added to the 4.2.x builds as well. 4.3.4 is the latest public alpha build and still exhibits the same issue.
The fix has not shipped yet. It will be in the next alpha, whenever that is released.