in air22,use URLLOADER access the website and download files generate a 2032 error

[xiaoyangsss]

In version air19 , we use the URLRequest and URLLoader in ios devices (ios version 10.0.0) can access http://kyt.jxt189.com/ydt/flash/kyt/UpdateContent.xml in ios, and we can in ios devices (ios version 10.0.0) download the XML file. but in version air22. when we download the XML in ios devices (ios version 10.0.0) , 2023 error will occur, what reason be excuse me?

[kglad]

i don't see a problem in the air ios simulator using air 22.  do you?

[jadams602 · Accepted solution]

Starting with AIR SDK 20, the AIR Runtime is now built with the iOS 9 SDK, this opens up the new requirement from Apple about App Transport Security:

Flash Player Help | Release Notes | Flash Player® 20 AIR® 20

Certainly sounds like you are running into missing NSAppTransportSecurity settings in your app descriptor if you are trying to use http: URLs and not https:

For example, like the following discussion:

URLLoader iOS - Error #2032: Stream Error « Starling Forum

[xiaoyangsss]

3Q. we solved this problem by NSAppTransportSecurity settings in my app descriptor.

thanks a lot!

[xiaoyangsss]

we add a xmllist(

  <dict>

  <key>NSAllowsArbitraryLoads</key>

  <true/>

  </dict>

)

into the info.plist,we were able to get  server's data by urlloader.

and we can run our IPA in our network well. every functions of our IPA can work.

but when we send the ipa to AppStore, the AppStore staff said that they can't login in the server in our IPA,which meant they cant access our server url(http://kyt.jxt189.com) by our IPA.

also, we requseted they open our server url(http://kyt.jxt189.com) by Safari.they said that they can't access the web.

if there any configuration had not been performed in our ipa?why they can't login in our server but we can?

thx

[jadams602]

So it looks like you decided to just completely disable App Transport Security by using <key>NSAllowsArbitraryLoads</key><true/>

If your app is really only going to one site "kyt.jxt189.com"  you should really consider adding more specialized App Transport Security exceptions that focus on allowing only jxt189.com and not the whole internet. At some point Apple might not allow you to just disable App Transport Security completely if you aren't building a general purpose web browsing app.

Regardless though, if they said something like "they can't login in the server in our IPA", maybe they mean you need to provide them a test username and password to login to the site to properly test the app? I don't think this new issue of theirs has anything to do with App Transport Security at all now, you have completely disabled ATS in your app...

[xiaoyangsss]

Very grateful for you taking time to give me suggsetion.

The site "kyt.jxt189.com" is not only one which is uesd by us in our app.

they said that  "they can't login in the server in our IPA",  the detail below is that they open our app in IOS 9.3.2 on IPV6-only network.

They input the username and password we provide ,then app showed a message that  the app can't connet to the web,which is we haven't seen in our network,only if we open app and login in with no wifi.

We completely  sure that we have set ATS in our app, and we can connet to the web in our app by our network but in Apple's network can't.

Is it possible that the problem is our web domain name can't be parsed to a correct IP by their network?

Is it possible that they can't connet to our website by their network(IPV6-only or USA Network or Apple's private network)?

[jadams602]

Are you using any ANEs (native extensions) in your app to determine whether you are connected to the internet/network?

Adobe has already said their use of URLs is IPv6-only-network compliant, but if you have any ANEs in your app that are doing their own 'network connected' code they might be using IPv4 only APIs.

If Apple is flagging an issue related to IPv6 network, you can test this locally yourself with your own Mac and see if you can reproduce the problem, links at the end of this thread: IOS submission refused because of IPv6 only