We have a QR code reader application, so we ingest many different kinds of URLs with different schemes, and we want to send them on to their handler applications. The new canOpenURL: security is understandable, but a problem for our user experience. Is there any way to opt out of this behavior? I understand Apple wants to migrate to Universal Links, but we already have a lot of content out there and would like to be able to transition in a more orderly manner.
As a fallback we probably could just start hardcoding our common schemes, but I was wondering if for our use case there was another way around.