App Transport Security - AllowsArbitraryLoads will not be allowed as of January 1st 2017

Solar2D iOS
#1

As of January 1st 2017, Apple will make it mandatory for all new app store submissions and app updates to have ATS enabled and will no longer support the AllowsArbitraryLoads exception.

We use quite a lot of ad providers (Vungle, Chartboost, AppLovin, Supersonic, FBAN, and AddBuddiz) and were wondering how they will be effected by this change. 

In the past I know Vungle would not work without setting “AllowsArbitraryLoads” to true, but I no longer see that limitation in the doc, so was that changed? 

I still see it in Chartboost and Supersonic however, so is it still required there as well?

Bottom line - we currently have the following in build.settings:

NSAppTransportSecurity = {     NSAllowsArbitraryLoads = true, },

How should we change it so we can pass the apple review, but keep using the ad providers?

Will the Facebook plugin be effected by this?

Thanks!

#2

Interestingly enough, I just started this conversation with the team this morning. The low down is that we are a the mercy of the provider. They have to provide an SDK that does not require ATS exceptions and they are moving along at various paces. Some providers have updated, some have not. I don’t have a list of who has updated and who has not unfortunately.

The simplest way to test things is to set the NSAllowsArbitraryLoads to false and run your app and look for errors in the console log. We will likely know more as we get closer.

Rob 

#3

Thanks for the quick reply, Rob. 

I know Vungle’s latest SDK (iOS SDK 4.0.9) supports the ATS changes, but I have no idea which SDK is used in the plugin. 

AppLovin also claims to be ATS compliant as of SDK version 3.1.2, but again I don’t know which SDK version is used by the plugin. 

Chartboost is also supposed to be ATS compliant, but the Corona docs still ask for NSAllowsArbitraryLoads to be true. 

In regards to other providers, I’m not sure which should work and which not, but I assume those who don’t will update their SDK soon, so will the Corona team be alert to these changes? 

#4

I don’t have a lot of visibility. Vungle maintains their own plugin and they did say in their last commit message that it’s the 4.0.9 sdk, so things should be good there. 

The others I can’t tell. I’ll share this with the team and see if they have any additional insight.

Rob

#5

I saw this post by Facebook stating we should use their SDK version 4.18+ to make sure it is ATS compliant and compatible with iOS 10, so I was just wondering which SDK version is used by the FBAN plugin?

#6

I’m not sure what version we are using. But we will update FBAN at some point because we are very aware of the concerns over ATS (though Apple seems to have backed off for now).

Watch the forums because we are starting to post when plugins get updated and the release note should cover the ATS status when we do.

Rob

#7

@stanga

I’m currently in the process of updating the FBAN plugin to 4.18.

My plan is to have an update ready by the end of the week. I’ll post an announcement on the forum once it’s live.

#8

Interestingly enough, I just started this conversation with the team this morning. The low down is that we are a the mercy of the provider. They have to provide an SDK that does not require ATS exceptions and they are moving along at various paces. Some providers have updated, some have not. I don’t have a list of who has updated and who has not unfortunately.

The simplest way to test things is to set the NSAllowsArbitraryLoads to false and run your app and look for errors in the console log. We will likely know more as we get closer.

Rob 

#9

Thanks for the quick reply, Rob. 

I know Vungle’s latest SDK (iOS SDK 4.0.9) supports the ATS changes, but I have no idea which SDK is used in the plugin. 

AppLovin also claims to be ATS compliant as of SDK version 3.1.2, but again I don’t know which SDK version is used by the plugin. 

Chartboost is also supposed to be ATS compliant, but the Corona docs still ask for NSAllowsArbitraryLoads to be true. 

In regards to other providers, I’m not sure which should work and which not, but I assume those who don’t will update their SDK soon, so will the Corona team be alert to these changes? 

#10

I don’t have a lot of visibility. Vungle maintains their own plugin and they did say in their last commit message that it’s the 4.0.9 sdk, so things should be good there. 

The others I can’t tell. I’ll share this with the team and see if they have any additional insight.

Rob

#11

I saw this post by Facebook stating we should use their SDK version 4.18+ to make sure it is ATS compliant and compatible with iOS 10, so I was just wondering which SDK version is used by the FBAN plugin?

#12

I’m not sure what version we are using. But we will update FBAN at some point because we are very aware of the concerns over ATS (though Apple seems to have backed off for now).

Watch the forums because we are starting to post when plugins get updated and the release note should cover the ATS status when we do.

Rob

#13

@stanga

I’m currently in the process of updating the FBAN plugin to 4.18.

My plan is to have an update ready by the end of the week. I’ll post an announcement on the forum once it’s live.