Post

Replies

Boosts

Views

Activity

Reply to URLComponent does not accept IPv6 address as host in iOS 16
Apple engineer confirmed that this is the expected behaviour: According to RFC 2732 Section 2, IPv6 addresses must be enclosed in [ and ] when it’s part of an URL. In this particular case, the host should be ipv6URLComponents.host = “[2001:0000:3238:dfe1:0063:0000:0000:fefb]”. I can confirm that the suggested solution works in iOS 16. However, the problem is that it is only a workaround, since enclosing IPv6 address in [] does not work in iOS 15 and older. So I still need to use if #available(iOS 16.0, *) {} syntax if I want my code to work in both iOS 15 and 16. I don't expect any updates regarding the issue. Just posting this in case someone with the same problem lands here.
Topic: App & System Services SubTopic: General Tags:
Aug ’22
Reply to App upgrade on iOS 16 while VPN connected routes traffic outside VPN tunnel
Report ID: FB11522371
Replies
Boosts
Views
Activity
Sep ’22
Reply to App upgrade on iOS 16 while VPN connected routes traffic outside VPN tunnel
Thanks for the quick reply. Sure, I'm aware that this is not the best place to place bug reports. I post here in hope to hear a confirmation from other developers before filing a bug report.
Replies
Boosts
Views
Activity
Sep ’22
Reply to URLComponent does not accept IPv6 address as host in iOS 16
Apple engineer confirmed that this is the expected behaviour: According to RFC 2732 Section 2, IPv6 addresses must be enclosed in [ and ] when it’s part of an URL. In this particular case, the host should be ipv6URLComponents.host = “[2001:0000:3238:dfe1:0063:0000:0000:fefb]”. I can confirm that the suggested solution works in iOS 16. However, the problem is that it is only a workaround, since enclosing IPv6 address in [] does not work in iOS 15 and older. So I still need to use if #available(iOS 16.0, *) {} syntax if I want my code to work in both iOS 15 and 16. I don't expect any updates regarding the issue. Just posting this in case someone with the same problem lands here.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Aug ’22
Reply to URLComponent does not accept IPv6 address as host in iOS 16
Thanks for the response. Yes, the problem persists on iOS 16.0b4 as well. I submitted a bug - FB11287912
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Aug ’22
Reply to Apple Services not available when connected to VPN with Custom DoH/DoT DNS
Hi! From what I can see, the issue is still not fixed. Is there any info about this one? Tested in iOS & iPadOS 15.2 Beta 4.
Replies
Boosts
Views
Activity
Dec ’21
Reply to iOS 14 NEHotspotNetwork fetchCurrent method completion block not called
I can confirm that the issue is fixed on iOS 15.1 RC / public release. NEHotspotNetwork.fetchCurrent is now working as expected.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Oct ’21
Reply to iOS 14 NEHotspotNetwork fetchCurrent method completion block not called
The issue is still not fixed on iOS 15 GM.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’21
Reply to iOS 14 NEHotspotNetwork fetchCurrent method completion block not called
When i run the same project on iOS 15 Beta 3 device, the NEHotspotNetwork.fetchCurrent callback always return a nil object. The issue is still present on my end on iOS 15 Beta 8.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’21
Reply to iOS 14 NEHotspotNetwork fetchCurrent method completion block not called
Thanks for the quick response! Bug report is submitted. ID: FB9361196
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’21
Reply to iOS 14 NEHotspotNetwork fetchCurrent method completion block not called
Has anyone tested NEHotspotNetwork.fetchCurrent on iOS 15? I have a project (with NETunnelProviderManager) which when i run on iOS 14.6 device everything works as expected. When i run the same project on iOS 15 Beta 3 device, the NEHotspotNetwork.fetchCurrent callback always return a nil object.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’21