Post not yet marked as solved
Normally, MFI isn't needed if you just want to achieve GATT over BR/EDR and your accessory supports it.
Post not yet marked as solved
Hello, did you have any news about this ?
It seems that the bluetooth API from External Accessory has been removed from recent SDKs.
Post not yet marked as solved
It is mind-boggling that there isn't a simple API, even a simple boolean or an enum value on UIApplication like UIApplication.localNetworkAccessAuthorizationStatus where we could simply check this. We have various flows where we want to delay and/or control the apparition of the system alert due to internal sockets being opened and we have to finally rely on a Network browser object to somewhat control it...
Post not yet marked as solved
Take a look at this thread about the same issue (but still no solution)
Post not yet marked as solved
Up please ! I filed a feedback about this issue using Feedback Assistant the 07/31/2019 with still no response (FB6871136)...
Post not yet marked as solved
Ok so I confirm that the issue is still present in iOS 13.2.It happens less often because I did not reproduce the bug myself on my debug devices, however some of our clients using iOS 13.2 still see a specific screen we made in our app that pops up whenever the returned SSID is nil (and again, even though we are appropriate permissions).Unfortunately, I don't have those profiles installed so I'll install those right now and if the issue happens, I'll file a sysdiagnose.Thanks for keeping us informed!
Post not yet marked as solved
I just had the same issue this morning using our app and my personal phone (iPhone 11 Pro) as some of our beta testers reported it.I attached a debugger to my phone and confirmed that CNCopyCurrentNetworkInfo returns nil even if we have appopriate permissions due to new iOS 13 privacy enforcements. I confirm that a reboot fixed the issue.Do we have any idea if iOS 13.2 resolves this ? I did not installed a beta yet.
According to a feedback by an Apple engineer, it behaves as expected.It is due to the tccd daemon.
