-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PlatformNotSupportedException on 32bits devices (e.g. iPad 2 and iOS 9.3) #7083
Comments
Simulator does not crash on an iPad Air 2 with iOS 11. Sorry, no way to simulate iOS 10 anymore. |
The inner exception tells you what's happening The You're running into another issue which is that the iPad 2 is a 32bits (only) device. So bindings for 64bits only API are not present (hence the easier to diagnose If you want to support older devices / iOS versions then you must ensure you either:
|
Sorry, while the above is true, you instantiated a |
… .ctor Types that are new in 64bits only OS are generated differently on 32bits bindings. They mainly throw a `PlatformNotSupportedException` so it's easier to diagnose (than a crash) what's happening at runtime. This works well in all cases except one. When a new type, let's say `UIMenuElement` is added **and** serves as a new base type for existing types. `UIKeyCommand` (iOS 7) -> `UICommand` (iOS 13)-> `UIMenuElement` (iOS 13) This is _correct_ as new base types can be added (in ObjC and C#). However the generated code for the constructors of `UICommand` and `UIMenuElement` would be throwing a `PlatformNotSupportedException` which breaks the `UIKeyCommand` on 32 bits devices. We fixed this in a few places by tweaking the availability attribute but that requires spotting the new base type while doing bindings and that is error prone [1][2]. This PR simply does let the `protected` constructor, using when chaining, be generated normally. It's simpler and will cover all the cases (without requiring hacks in the availability of those types) [1] xamarin#7083 [2] xamarin#7084
… .ctor (#7085) Types that are new in 64bits only OS are generated differently on 32bits bindings. They mainly throw a `PlatformNotSupportedException` so it's easier to diagnose (than a crash) what's happening at runtime. This works well in all cases except one. When a new type, let's say `UIMenuElement` is added **and** serves as a new base type for existing types. `UIKeyCommand` (iOS 7) -> `UICommand` (iOS 13)-> `UIMenuElement` (iOS 13) This is _correct_ as new base types can be added (in ObjC and C#). However the generated code for the constructors of `UICommand` and `UIMenuElement` would be throwing a `PlatformNotSupportedException` which breaks the `UIKeyCommand` on 32 bits devices. We fixed this in a few places by tweaking the availability attribute but that requires spotting the new base type while doing bindings and that is error prone [1][2]. This PR simply does let the `protected` constructor, using when chaining, be generated normally. It's simpler and will cover all the cases (without requiring hacks in the availability of those types) [1] #7083 [2] #7084
Fixed in |
… .ctor Types that are new in 64bits only OS are generated differently on 32bits bindings. They mainly throw a `PlatformNotSupportedException` so it's easier to diagnose (than a crash) what's happening at runtime. This works well in all cases except one. When a new type, let's say `UIMenuElement` is added **and** serves as a new base type for existing types. `UIKeyCommand` (iOS 7) -> `UICommand` (iOS 13)-> `UIMenuElement` (iOS 13) This is _correct_ as new base types can be added (in ObjC and C#). However the generated code for the constructors of `UICommand` and `UIMenuElement` would be throwing a `PlatformNotSupportedException` which breaks the `UIKeyCommand` on 32 bits devices. We fixed this in a few places by tweaking the availability attribute but that requires spotting the new base type while doing bindings and that is error prone [1][2]. This PR simply does let the `protected` constructor, using when chaining, be generated normally. It's simpler and will cover all the cases (without requiring hacks in the availability of those types) [1] xamarin#7083 [2] xamarin#7084
@spouliot ETA when this will be available? |
… chaining .ctor (#7092) Types that are new in 64bits only OS are generated differently on 32bits bindings. They mainly throw a `PlatformNotSupportedException` so it's easier to diagnose (than a crash) what's happening at runtime. This works well in all cases except one. When a new type, let's say `UIMenuElement` is added **and** serves as a new base type for existing types. `UIKeyCommand` (iOS 7) -> `UICommand` (iOS 13)-> `UIMenuElement` (iOS 13) This is _correct_ as new base types can be added (in ObjC and C#). However the generated code for the constructors of `UICommand` and `UIMenuElement` would be throwing a `PlatformNotSupportedException` which breaks the `UIKeyCommand` on 32 bits devices. We fixed this in a few places by tweaking the availability attribute but that requires spotting the new base type while doing bindings and that is error prone [1][2]. This PR simply does let the `protected` constructor, using when chaining, be generated normally. It's simpler and will cover all the cases (without requiring hacks in the availability of those types) [1] #7083 [2] #7084
Hi, My build config is XF 4.1 Thanks. |
The crash happens only on 32bits devices (or if you're building 32bits only on a old version of iOS that supports 32/64bits). Xamarin.Forms itself hits the issue when it calls At the moment the fix is only available of our upcoming Xcode11.1 branch. You can get a package directly from our bots here: https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/xcode11.1/6bdce2dac8a3c3946c4e464af5e8355360d79dfc/12/package/notarized/xamarin.ios-13.3.0.6.pkg This has not gone thru any formal tests, beside automated ones, but the branch is still very similar to the stable release. Notes
|
Indeed, the changes are not big: xamarin-mac-6.2.0.42...xcode11.1 |
Excellent! I confirm that my app is not crashing anymore! Thanks a bunch! |
Thanks this fix works. |
@spouliot Does this work with Visual studio 2019 community or preview VS? |
@LeoJHarris Just install the package on top of the current stable channel of VS community and it will work. |
@spouliot We downloaded the package linked above onto our mac and installed that there and then prompted to install on windows machine on Visual studio start up connecting to the mac. When we run our app on a tablet running iOS 10.3 are still getting a PlatformNotSupportedException as shown below: Can you please advise if we need to open a new ticket for this? This is a blocking issue for us. 2019-09-26 09:22:02.574 MyApp.iOS[945:184528] [AppCenterCrashes] ERROR: +[MSWrapperLogger MSWrapperLog:tag:level:]/10 Unhandled Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.PlatformNotSupportedException: This API is not supported on this version of iOS
at UIKit.UIMenuElement..ctor (System.IntPtr handle) [0x00007] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIMenuElement.g.cs:91
at UIKit.UICommand..ctor (System.IntPtr handle) [0x00000] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UICommand.g.cs:88
at UIKit.UIKeyCommand..ctor (System.IntPtr handle) [0x00000] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKeyCommand.g.cs:91
at (wrapper managed-to-native) System.Reflection.RuntimeConstructorInfo.InternalInvoke(System.Reflection.RuntimeConstructorInfo,object,object[],System.Exception&)
at System.Reflection.R
untimeConstructorInfo.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x00005] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:936
--- End of inner exception stack trace ---
at System.Reflection.RuntimeConstructorInfo.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x00018] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:944
at System.Reflection.RuntimeConstructorInfo.DoInvoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00086] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:926
at System.Reflection.RuntimeConstructorInfo.In
voke (System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:960
at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/external/corefx/src/Common/src/CoreLib/System/Reflection/ConstructorInfo.cs:22
at ObjCRuntime.Runtime.ConstructNSObject[T] (System.IntPtr ptr, System.Type type, ObjCRuntime.Runtime+MissingCtorResolution missingCtorResolution) [0x0003b] in <1b20576ce73640d782f136af13e79af3>:0
at ObjCRuntime.Runtime.GetNSObject[T] (System.IntPtr ptr) [0x000d1] in <1b20576ce73640d782f136af13e79af3>:0
at UIKit.UIKeyCommand.Create (Foundation.NSString keyCommandInput, UIKit.UIKeyModifierFlags modifierFlags, ObjCRuntime.Selector action) [0x0003b] in /Library/Frame
works/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKeyCommand.g.cs:107
at Xamarin.Forms.Platform.iOS.VisualElementRenderer`1[TElement]..ctor () [0x00043] in <4e367b2cd46d4a02b980ea2aa2a1115b>:0
at Xamarin.Forms.Platform.iOS.Platform+DefaultRenderer..ctor () <0x18d7ee0 + 0x0004f> in <4e367b2cd46d4a02b980ea2aa2a1115b#f28c7bdbefdddcba928d508479031273>:0
at Xamarin.Forms.Platform.iOS.Platform.CreateRenderer (Xamarin.Forms.VisualElement element) [0x00000] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Platform.cs:187
at Xamarin.Forms.Platform.iOS.VisualElementPackager.OnChildAdded (Xamarin.Forms.VisualElement view) [0x0003d] in d:\a\1\s\Xamarin.Forms.Platform.iOS\VisualElementPackager.cs:97
at Xamarin.Forms.Platform.iOS.VisualElementPackager.Load () [0x0001e] in d:\a\1\s\Xamarin.Forms.Platform.iOS\VisualElementPackager.cs:46
at Xamarin.Forms.Platform.iOS.PageRenderer.ViewDidLoad () [0x0008f] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\PageRenderer.cs:238
at (wrapper managed-to-nativ
e) ObjCRuntime.Messaging.IntPtr_objc_msgSendSuper(intptr,intptr)
at UIKit.UIViewController.get_View () [0x0002a] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIViewController.g.cs:3171
at Xamarin.Forms.Platform.iOS.PageRenderer.get_NativeView () [0x00000] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\PageRenderer.cs:104
at Xamarin.Forms.Platform.iOS.PageRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x0003d] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\PageRenderer.cs:120
at Xamarin.Forms.Platform.iOS.Platform.CreateRenderer (Xamarin.Forms.VisualElement element) [0x00014] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Platform.cs:188
at Xamarin.Forms.Platform.iOS.NavigationRenderer.CreateViewControllerForPage (Xamarin.Forms.Page page) [0x00008] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\NavigationRenderer.cs:358
at Xamarin.Forms.Platform.iOS.NavigationRenderer.OnPushAsync (Xamarin.Forms.Page page, System.Boolean animated) [0x0001d] in d:\a\1
\s\Xamarin.Forms.Platform.iOS\Renderers\NavigationRenderer.cs:345
at Xamarin.Forms.Platform.iOS.NavigationRenderer.<ViewDidLoad>b__46_0 (Xamarin.Forms.Page p) [0x00024] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\NavigationRenderer.cs:238
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/AsyncMethodBuilder.cs:1021
at Foundation.NSAsyncSynchronizationContextDispatcher.Apply () [0x00000] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/Foundation/NSAction.cs:178
at (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr)
at UIKit.UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate) [0x00005] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKit/UIAppl
ication.cs:86
at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) [0x0000e] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKit/UIApplication.cs:65
at MyApp.iOS.Application.Main (System.String[] args) [0x00001] in C:\Users\Admin\Apps\MyApp\MyApp\MyApp.iOS\Main.cs:18
2019-09-26 09:22:02.669 MyApp.iOS[945:184528] Unhandled managed exception: Exception has been thrown by the target of an invocation. (System.Reflection.TargetInvocationException)
at System.Reflection.RuntimeConstructorInfo.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x00018] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:944
at System.Reflection.RuntimeConstructorInfo.DoInvoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00086] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:926
at System.Reflection.RuntimeConstructorInfo.Invoke (System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globali
zation.CultureInfo culture) [0x00000] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:960
at System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters) [0x00000] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/external/corefx/src/Common/src/CoreLib/System/Reflection/ConstructorInfo.cs:22
at ObjCRuntime.Runtime.ConstructNSObject[T] (System.IntPtr ptr, System.Type type, ObjCRuntime.Runtime+MissingCtorResolution missingCtorResolution) [0x0003b] in <1b20576ce73640d782f136af13e79af3>:0
at ObjCRuntime.Runtime.GetNSObject[T] (System.IntPtr ptr) [0x000d1] in <1b20576ce73640d782f136af13e79af3>:0
at UIKit.UIKeyCommand.Create (Foundation.NSString keyCommandInput, UIKit.UIKeyModifierFlags modifierFlags, ObjCRuntime.Selector action) [0x0003b] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKeyCommand.g.cs:107
at Xamarin.Forms.Platform.iOS.Visual
The app has been terminated.ElementRenderer`1[TElement]..ctor () [0x00043] in <4e367b2cd46d4a02b980ea2aa2a1115b>:0
at Xamarin.Forms.Platform.iOS.Platform+DefaultRenderer..ctor () <0x18d7ee0 + 0x0004f> in <4e367b2cd46d4a02b980ea2aa2a1115b#f28c7bdbefdddcba928d508479031273>:0
at Xamarin.Forms.Platform.iOS.Platform.CreateRenderer (Xamarin.Forms.VisualElement element) [0x00000] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Platform.cs:187
at Xamarin.Forms.Platform.iOS.VisualElementPackager.OnChildAdded (Xamarin.Forms.VisualElement view) [0x0003d] in d:\a\1\s\Xamarin.Forms.Platform.iOS\VisualElementPackager.cs:97
at Xamarin.Forms.Platform.iOS.VisualElementPackager.Load () [0x0001e] in d:\a\1\s\Xamarin.Forms.Platform.iOS\VisualElementPackager.cs:46
at Xamarin.Forms.Platform.iOS.PageRenderer.ViewDidLoad () [0x0008f] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\PageRenderer.cs:238
at (wrapper managed-to-native) ObjCRuntime.Messaging.IntPtr_objc_msgSendSuper(intptr,intptr)
at UIKit.UIViewController.get_View () [0x0002a] in /Libra
Failed to Stop app: An error occurred on client IDB1630274 while executing a reply for topic xvs/idb/16.3.0.274/stop-app
ry/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIViewController.g.cs:3171
at Xamarin.Forms.Platform.iOS.PageRenderer.get_NativeView () [0x00000] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\PageRenderer.cs:104
at Xamarin.Forms.Platform.iOS.PageRenderer.SetElement (Xamarin.Forms.VisualElement element) [0x0003d] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\PageRenderer.cs:120
at Xamarin.Forms.Platform.iOS.Platform.CreateRenderer (Xamarin.Forms.VisualElement element) [0x00014] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Platform.cs:188
at Xamarin.Forms.Platform.iOS.NavigationRenderer.CreateViewControllerForPage (Xamarin.Forms.Page page) [0x00008] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\NavigationRenderer.cs:358
at Xamarin.Forms.Platform.iOS.NavigationRenderer.OnPushAsync (Xamarin.Forms.Page page, System.Boolean animated) [0x0001d] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\NavigationRenderer.cs:345
at Xamarin.Forms.Platform.iOS.NavigationRenderer.<ViewD
The app has been terminated.
idLoad>b__46_0 (Xamarin.Forms.Page p) [0x00024] in d:\a\1\s\Xamarin.Forms.Platform.iOS\Renderers\NavigationRenderer.cs:238
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__7_0 (System.Object state) [0x00000] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/AsyncMethodBuilder.cs:1021
at Foundation.NSAsyncSynchronizationContextDispatcher.Apply () [0x00000] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/Foundation/NSAction.cs:178
at (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr)
at UIKit.UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate) [0x00005] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKit/UIApplication.cs:86
at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegate
ClassName) [0x0000e] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKit/UIApplication.cs:65
at MyApp.iOS.Application.Main (System.String[] args) [0x00001] in C:\Users\Admin\Apps\MyApp\MyApp\MyApp.iOS\Main.cs:18
--- inner exception ---
This API is not supported on this version of iOS (System.PlatformNotSupportedException)
at UIKit.UIMenuElement..ctor (System.IntPtr handle) [0x00007] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIMenuElement.g.cs:91
at UIKit.UICommand..ctor (System.IntPtr handle) [0x00000] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UICommand.g.cs:88
at UIKit.UIKeyCommand..ctor (System.IntPtr handle) [0x00000] in /Library/Frameworks/Xamarin.iOS.framework/Versions/13.2.0.42/src/Xamarin.iOS/UIKeyCommand.g.cs:91
at (wrapper managed-to-native) System.Reflection.RuntimeConstructorInfo.InternalInvoke(System.Reflection.RuntimeConstruc
torInfo,object,object[],System.Exception&)
at System.Reflection.RuntimeConstructorInfo.InternalInvoke (System.Object obj, System.Object[] parameters, System.Boolean wrapExceptions) [0x00005] in /Users/builder/jenkins/workspace/xamarin-macios/xamarin-macios/external/mono/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:936 |
@LeoJHarris, this is much strange, your stack trace is full of iOS framework 13.2.0.42, which is the stable one. Sounds odd, but after downloading, you should obviously install it, and you should better do so closing first VS. After installing and going to about, full info, you should read that the iOS framework is now 13.3.0.6, and not 13.2.0.42! |
@xperseguers I see the issue now I didnt fully read the message the first time and I clicked install to quickly (simple mistake). But I reinstalled onto the mac again the version 13.3.0.6: @spouliot However I cannot pair with mac now if I do not install previous stable version can you advise the work around? |
@spouliot Hi can you advise how we can use use 13.3.0.6? We have it installed on mac but Visual studio requires older and more stable Xamarin.ios of 13.2.0.42 for pairing. Please advice. |
I'm guessing this bug is going to break our CI builds until the XCode 11.1 release is issued? |
@LeoJHarris For now I was able to work around this issue by Using Visual Studio 2019 Preview, which installed and earlier version 12.x |
Hi @IkeRolfe are you meaning that the Visual Studio 2019 preview you have is installed with older Xamarin.iOS 12.x ? If I do a fresh install of preview 2019 then I think that will include the latest Xamarin.iOS. |
@LeoJHarris I installed Preview 2019 today and it is still using 12.x for some reason. |
Hi everyone, we just released Xamarin.iOS 13.4 to stable. Here are the release notes mention the regression fix specifically: https://docs.microsoft.com/en-us/xamarin/ios/release-notes/13/13.4 |
… .ctor (xamarin#7085) Types that are new in 64bits only OS are generated differently on 32bits bindings. They mainly throw a `PlatformNotSupportedException` so it's easier to diagnose (than a crash) what's happening at runtime. This works well in all cases except one. When a new type, let's say `UIMenuElement` is added **and** serves as a new base type for existing types. `UIKeyCommand` (iOS 7) -> `UICommand` (iOS 13)-> `UIMenuElement` (iOS 13) This is _correct_ as new base types can be added (in ObjC and C#). However the generated code for the constructors of `UICommand` and `UIMenuElement` would be throwing a `PlatformNotSupportedException` which breaks the `UIKeyCommand` on 32 bits devices. We fixed this in a few places by tweaking the availability attribute but that requires spotting the new base type while doing bindings and that is error prone [1][2]. This PR simply does let the `protected` constructor, using when chaining, be generated normally. It's simpler and will cover all the cases (without requiring hacks in the availability of those types) [1] xamarin#7083 [2] xamarin#7084
Steps to Reproduce
Expected Behavior
The application should not crash.
Actual Behavior
The application is crashing. Could not get a stacktrace with this project but with a real project of mine, and although I have other 3rd-party libraries initialization lines crashing earlier, it seems to crash as well with:
with inner exception:
Environment
Example Project
https://docs.microsoft.com/en-gb/samples/xamarin/xamarin-forms-samples/userinterface-xaminals/
The text was updated successfully, but these errors were encountered: