Thanks! This may be that you are trying to communicate with the device directly after association and that is why you are receiving these errors. If so, add a small delay in to allow for the IP and the association to setup correctly. I am attempting the connection only when the completionHandler gets called, which seems to be as soon as user is done with the system dialog? Meaning they either press "Join" or decline. Then I have 0.5 second delay before attempting to access data from the game console in this case. Unless the completionHandler is somehow called multiple times, I have no idea how accessing the device (or trying to) could lead to errors I am seeing? There is also this one: NEHotspotConfigurationErrorAlreadyAssociated which I would expect to get in cases where I am attempting to join the same network for second time, but I haven't got this one yet. Also, there have been some issue using the flag for joinOnce in iOS 15 Hmm this possibly be it, as I am indeed using this flag. The majority of devices that report the mentioned erros are various versions of iOS 15, but not all of them. Since disconnect should happen as soon as the game console stops providing network, I think I can safely remove this flag and see if there are any changes.

Thanks for the details! I had no idea regarding timing. Changed it to 3 seconds + removed the joinOnce flag. I am going to do phased release and will monitor Sentry regarding these issues.

It looks like the "conversion" to new buffer with the stride is causing issues. When I try saving the original pcmBuffer the callback returns I can hear the sound.

Finally (and unfortunately) managed to reproduce the issue. VPN stays in the "Connecting..." state indefinitely. It also does not help to try "re-starting" it in the settings. Even when I start tunnel from different app which works fine and attempt to start tunnel for my app, it again gets stuck at "Connecting" Here are the logs. The bottom three messages keep repeating over and over again. NESMVPNSession[Primary Tunnel:AppBlock Blocker:EC537A50-9463-4CAA-9A89-B67EE9316BDB:(null)]: status changed to connecting NESMVPNSession[Primary Tunnel:AppBlock Blocker:EC537A50-9463-4CAA-9A89-B67EE9316BDB:(null)]: got On Demand start message from pid 117 NESMVPNSession[Primary Tunnel:AppBlock Blocker:EC537A50-9463-4CAA-9A89-B67EE9316BDB:(null)]: Received a start command from rapportd[89] NESMVPNSession[Primary Tunnel:AppBlock Blocker:EC537A50-9463-4CAA-9A89-B67EE9316BDB:(null)]: Skip a start command from rapportd[89]: session in state connecting Sometimes when "Connecting..." internet does not work at all on the device, sometimes it does

Thanks. From the above issue, the only way to resolve it is by: Restarting the device Deleting the VPN and installing it again Re-install the entire app Switching to different VPN does not help, which suggests to me that there is some wrong state that persists?

Thanks both! That was it! Once I saw the error it did not occur to me to check how the interaction is set up. Also note for others trying this, you need to enable user interaction on the UIImageView otherwise the Live Text button does not work.

With the beta 2 of iOS 16 and Xcode 14, this now appears to work as expected.

Thanks @eskimo! We inspected the form yesterday but it looked to us as something from iOS 15, when Screen Time was strictly for parental control apps and could be used only in Parent/Guardian - Child setup. Whereas with iOS 16, Screen Time API can be used for individual devices.

So we got the entitlement for distribution but I still have the same problem: I tried removing the developer capability in Apple Developer portal and keeping just the Distribution one but did not help.

Thanks! In the end it looks like the issue was entitlement for one of the app's extensions. We tried various things and finally got it to upload.

Hmm you are right, I seem to remember this limitation but have no idea where I first spotted it and cannot find it now. So perhaps I misremember this requirement. These methods are also available on macOS - so I thought that having multiple VPN configs works there.

Thanks @gchiste! I will look into the VNDetectRectanglesRequest and file the enhancement request.

Having the same problem. thought it was maybe because we use Screen Time API but dunno. Yesterday all builds worked fine and we did not make any entitlements changes.

Thanks! The crash we are seeing isn't related to any external dependency which both the solution posted seem to solve. I am tempted to try changing the "Dead Code Stripping" but I am afraid of other repercusions this could have.

Hi, even if you search the device for "App Store" you cannot find it? iOS sometimes doesn't "return" App Store icon to the same place it used to be.