iOS10 network.request not working. Can't submit fix because of app thinning error. Help?

Solar2D iOS
#1

I have a Corona made app that uses network.request with POST to make requests to a custom game server. The game server is hosted on a 3rd party VPS and has an SSL cert and I use https:// and a subdomain name to access it. However I don’t think my server has its own IP address (though I kind of remember setting up an individual IP)  the control panel seems to be saying it is using SNI.  Is that not ok with iOS10?

On iOS10 connections do not work and my customers cannot play.  Is it the new ipV6 requirements that are making this not work? Does anyone have a good link that describes what these new requirements mean?

I can get my app to work if I add 

NSAppTransportSecurity =

{

NSAllowsArbitraryLoads = true,

},

to the build.settings. I am assuming this is not ideal (but I am also unsure exactly what this does), but I am willing to go with it, except when I tried to submit my app I am getting the app thinning bitcode error.  

I need to fix my app asap, but apparently can’t submit an update. Does anyone have any ideas of something I can do on the server side to appease iOS10?  

I attached a dump of logging from my ipad (but here are some lines that look like they may be meaningful):

Sep 13 20:04:19 Lauras-ipad mDNSResponder[88] <Info>: ShouldSuppressUnicastQuery: Query suppressed for ******, qtype AAAA, since DNS Configuration does not allow (req_A is true and req_AAAA is false)

Sep 13 20:04:19 Lauras-ipad symptomsd(SymptomEvaluator)[108] <Info>: [0.008]   285 OFC Poker         SYMPTOM_LIBNETCORE_TLS_HANDSHAKE_FAILED  libne 00000002 0000011d -------- -------- [4 <6f666361 70702e63 6f727669 64617070 732e636f 6d3a3434 3300>] [3 <4f464320 506f6b65 7200>] [2 <52114335 48443492 86fa0626 9983dc34>]

Thanks
 

#2

Ran this test on my server: https://www.ssllabs.com/ssltest/ and it came up with some errors including TLS 1.0 and RC4 which I think Apple says is an issue in iOS10.  Contacted my host and they said they would upgrade stuff.  Hopefully they do it soon and it works.

#3

The app thinning issue should be solved, but you will have to update to daily build 2016.2948 or later. As for the iOS 10 networking issues, Apple has been enforcing connections go to https:// (SSL) servers since iOS 9. The provided that bit of plist code where you’re doing arbitrary loads for people to get by until they can go all https:.  If adding that code makes your app work, you are somewhere along the way connecting to an http:// (non SSL ) server instead of https://.  By the end of the year, Apple is going to take that away and require everything go to https:

Apple is also requiring all apps to work over IPv6 which means you can’t use IP addresses, you have to use Domain Names, which it sounds like you are.

Rob

#4

Thanks Rob for the answer and it is good to know the app thinning error is fixed.  Fortunately I do not need to send an update now because it was the TLS1.0 and RC4 settings on the server–those are no longer supported in iOS10.  My host updated those settings and now it works. :slight_smile:  

#5

Ran this test on my server: https://www.ssllabs.com/ssltest/ and it came up with some errors including TLS 1.0 and RC4 which I think Apple says is an issue in iOS10.  Contacted my host and they said they would upgrade stuff.  Hopefully they do it soon and it works.

#6

The app thinning issue should be solved, but you will have to update to daily build 2016.2948 or later. As for the iOS 10 networking issues, Apple has been enforcing connections go to https:// (SSL) servers since iOS 9. The provided that bit of plist code where you’re doing arbitrary loads for people to get by until they can go all https:.  If adding that code makes your app work, you are somewhere along the way connecting to an http:// (non SSL ) server instead of https://.  By the end of the year, Apple is going to take that away and require everything go to https:

Apple is also requiring all apps to work over IPv6 which means you can’t use IP addresses, you have to use Domain Names, which it sounds like you are.

Rob

#7

Thanks Rob for the answer and it is good to know the app thinning error is fixed.  Fortunately I do not need to send an update now because it was the TLS1.0 and RC4 settings on the server–those are no longer supported in iOS10.  My host updated those settings and now it works. :slight_smile: