Custom scheme redirect iOS 11

Hi @all
We are facing the following problem. Our authentication service only accepts a https scheme for the redirect uri. So it is not possible to use a custom scheme for a deep linking into to app. So we have implemented a redirect page with a button, which references to a custom scheme like com.myapp://token=abcd1234. This solution works perfectly for iOS 10 and below. On iOS 11 where SFAuthenticationSession is used the library closes the web view without calling any callback. The library seems to block the callbacks when the redirect uri scheme doesn't match the custom scheme.

Is there a way to omit this behavior?

Start by tracing the iOS 11 SFAuthenticationSession redirect callback handling and compare it with the custom-scheme flow described in the issue. Verify how the library handles a redirect whose scheme differs from the configured callback scheme, then run the existing authentication tests or reproduce the flow on iOS 11. Done means the behavior is understood and the supported redirect behavior is documented or covered by a verified fix.