After I make an archive of my project, I want to submit it to TestFlight to beta test it.
If I export the archive from XCode using Ad Hoc Distribution and then install it on my device, everything works fine.
When I upload that same archive to App Store, some of Internet connectivity features do not work anymore. Specifically, the app cannot connect via websockets anymore.
What makes the app behave differently depending on distribution type and how can I solve the issue?
Thank you in advance.
It is possible that this is related to the security policies enforced by App Transport Security (ATS). If this is the case, it would explain the behavior as ATS is being enforced when the app is installed via TestFlight, but ATS is not enforced when installed via the ad hoc method.
ATS places security requirements on the servers that your app connects to. If the server does not meet the requirements, ATS will not allow the app to communicate with that server. For example, if the websockets server you are connecting to is just plain HTTP, the app will not be able to connect to it when ATS is enforced.
It is the responsibility of the developer to make sure servers under your control are updated to meet the security requirements. If the server is not under your control, there are options to allow exceptions. (App Review will make you justify the exceptions.)
Here is documentation on ATS:
Try following the instructions in the section "Debugging ATS Connections". That should help you to determine if ATS is actually the root cause for your issue.
Thank you for the reply. Websocket connection is done over SSL, so ATS settings were not a problem. I had to turn Enable Bitcode setting off, somehow it was messing with websocket connection.
