iOS 9 support

[ninaada]

Bug report best practices: Submitting Issues

Can you please bring down support version for iOS to 9, so that same features we can use for older iPads, which are in highest usage in enterprise. We love to use this, but can't leverage it throughout.

[thezik]

+1 for this. Leaving out iOS 9 means leaving out iPad 2 and iPad minis.
Also, for the sake of curiosity, which features are keeping you from giving iOS 9 support?
Maybe the Library may be used on iOS 9 unless some specific functionalities are used?

[jamesmontemagno]

As of right now we plan on supporting iOS 10+ and Android 4.4+ as each of these represent about 95%+ percent of the market. We don't do anything in the code to specifically cause issues on older versions, but we just don't officially support them at this time, which means that we don't do specific checks in code for iOS 9, only iOS 10 and 11. Code maintainability and accessing new features that come out including the marketshare is some of the key reasons we have this in place. I don't think there is any code that would crash on iOS 9 specifically today, but can not be guaranteed.

[OnShoreDev]

One feature that does not work in iOS 9 is opening a browser with:
`Browser.OpenAsync(uri, launchMode);

The app crashes.

[mattleibow]

@OnShoreDev DO you have a stack trace? Maybe we are using a method that does not exist.

[jamesmontemagno]

SFSafariViewController isn't supported on iOS 9 and you would want to use the External launch mode.

[OnShoreDev]

@OnShoreDev DO you have a stack trace? Maybe we are using a method that does not exist.

iOS Mini iPad Version 9.3.5 (13G36)

Code:
using Xamarin.Essentials;
Browser.OpenAsync(uri, launchMode); //launchMode is external

Stack Trace

Foundation.MonoTouchException: Objective-C exception thrown. Name: NSInvalidArgumentException Reason: -[.....Application openURL:options:completionHandler:]: unrecognized selector sent to instance 0x14dd5820
Native stack trace:
0 CoreFoundation 0x24d1f933 + 150
1 libobjc.A.dylib 0x244bae17 objc_exception_throw + 38
2 CoreFoundation 0x24d252b5 + 0
3 CoreFoundation 0x24d22ee1 + 700
4 CoreFoundation 0x24c4e238 _CF_forwarding_prep_0 + 24

[jamesmontemagno]

I put in a fix here on openasync, should be fixed up in next patch.

[OnShoreDev]

I put in a fix here on openasync, should be fixed up in next patch.

Great. When is the next patch scheduled?