Post not yet marked as solved
Update: this bug still exists in iOS 15 beta 3.
Is there any movement in the bug reports mentioned in this thread?
Post not yet marked as solved
I can confirm that this bug is still present in iOS15 beta 2.
Post not yet marked as solved
No, not exactly. In that case last year, manually set UA’s would not be respected in CONNECT requests for any NSURLRequests.
The behavior that I currently see is that no user agent whatsoever is passed for CONNECT requests. This feels quite arbitrary to me, as all other requests (GET/POST/…) do function as expected.
Post not yet marked as solved
I have the same question actually. I've posted about similar changes in iOS 14 before (https://developer.apple.com/forums/thread/657824). Is there any chance this can get reinstated?
Post not yet marked as solved
I reported a bug with ticket no 8889361.
Post not yet marked as solved
While debugging using a HTTPS proxy I often use the user agent to distinguish between requests. This can most certainly be done differently.
After writing this post, I realize that I might have misinterpreted the release notes. I now interpret this issue as being fixed since beta 4. Thanks for following up!
Post not yet marked as solved
Matt, thanks for your elaborate answer.
It turned out I was actually able to attach briefly, but a crash appeared that took me a while to understand. After paying close attention to the logs in the Console, I found out that the following message appeared just before the crash:
This copy of libswiftCore.dylib requires an OS version prior to 12.2.0 After reading about it online, I resolved this issue by adding /usr/lib/swift
as the first item in my Runtime Search Paths for the tunnel provider target.
After adding this item Instruments works as expected again. I'm not at all sure if it's at all related to Instruments at this point, but I hope that future readers find this useful.
The behavior I observe is the following: the update is successfully downloaded, but only installed once the extension is no longer active. Fortunately, this also happens after coming back from sleep. As a result, apps will eventually upgrade itself, albeit not on the very moment where a user hits the upgrade button in the app store. I would not call this a bug per se.
Post not yet marked as solved
This issue seems to be fixed on beta 5, although I did not see any mention of it in the release notes.
Post not yet marked as solved
I am still experiencing this issue on iOS11 beta 4. To be clear, all apps offering VPN via a packet tunnel provider have a serious issue as they are not able to update when enabled on iOS 11.
Post not yet marked as solved
Unfortunately this bug still exists on iOS 11 beta 4. Are there any plans to fix this issue?
Post not yet marked as solved
Thanks for following up, Eskimo. A bug was reported with bug number 33453549.
Post not yet marked as solved
A bug is reported with id 33453549. Hoping for a speedy fix!
