Any penalties for using NSAllowsArbitraryLoads?

Question

Created Jul ’15

Replies 1

Boosts 0

Participants 2

Hoping for an Apple response here, but the new App Transport Security feature has the potential to reek havock with one of our applications. We have to recursively probe networks and follow a series of URL redirects in order to obtain a form for posting login details too. These networks are out of our control, and contain hundreds of thousands of different operators and implementations. 99% of the redirect URL's are not HTTPS until the point to which we have to finally post the credentials, thus our App simply has to call non-https URL's.

Thankfully, we can disable App Transport Security through the 'NSAllowsArbitraryLoads' BOOL in the info.plist but will this have any negative consequences to our end users? Does Apple plan on alerting users to Apps which disable App Transport Security in the App Store?

Boost

Answer 1

gunjiira OP

Aug ’15

Very well phrased question, where we likewise are keen on more information from Apple. Just like written, enabling ATS on all related networks is a monumental task, so rather than consciously or not spreading fear in their developer community about it, forcing action, they should responsible reveal their timeline and the risks involved.

Apart from any alerts to users a la launching other apps via URL schemes, if/when 'NSAllowsArbitraryLoads' will be deprececated in the future is of elemental interest to iOS developers. There even might be phase before where it is still technically possible to disable ATS, but it might lead to rejections in App review.

0