The insane number of scheme checks fails on iOS 9

[sberrevoets]

The insane number of scheme checks fails on iOS 9

[briancaw]

Hi @sberrevoets,

Appboy only calls canOpenURL when we get a deep link (e.g. from push, in-app message, news feed); we certainly don't have any hardcoded or server configured URLs that we call canOpenURL on. We have also never seen this in our development or had a customer report of this issue.

This behavior looks like an SDK that is querying the device for installed applications (which isn't something we do). It also seems that people have had this problem before iOS9 - see http://forum.starling-framework.org/topic/app-rejected-because-it-uses-canopenurl-in-an-inappropriate-manner.

Maybe you have another SDK installed that is doing this?

[sberrevoets]

My apologies, based on the flow in our app it looked like Appboy was the culprit, but it turns out another SDK is responsible for this long list.

You mention that Appboy does call canOpenURL: - is this only with URLs that we ourselves provide, or on other non-Apple apps as well? If the latter, we'd need to whitelist those URLs so that they aren't blocked.

[billmag]

It's only when your company's dashboard users (or API driven messages) specify a deep link URL as a click action for any of our message types. If someone sends a message to your users specifying a deep link URL for another app, we will check it, but if you're only ever sending your own deep links, then it will just only be for Lyft.

Could you let us know which SDK it was so we can help others debug if this comes in through a support ticket?

[sberrevoets]

Thanks for verifying. We've run in quite a few libraries/apps that check all kinds of unrelated app schemes, but this list was particularly concerning as it actually blocked us from making legitimate queries.