When using the NEHotspotConfigurationManager applyConfiguration interface for network connection, there is a certain probability of encountering the "Unable to join network" error. We captured the system logs when the issue occurred, some errors are due to the network not being scanned, while others are rejected by the system（console logs like:WCLScanManager scan is blocked by other system activity 32 or 9）. If there are any methods to optimize or avoid these errors?
I have report a bug, bug number: FB19253647
That’s the best path forward for issues like this.
The Apple Developer Forums is primarily focused on APIs, and the NEHotspotConfigurationManager is pretty simple. If you’re able to use the API to successfully join the network in some cases then you’re using the API correctly. If you then encounter intermittent errors, that’s nothing to do with your use of the API and instead an issue deeper in the Wi-Fi stack. We can’t help you with that here on the forums, and hence a bug report is called for.
There is one titbit I’d like to pass along. On our Bug Reporting > Profiles and Logs page you’ll find specific instructions for how best to file a Wi-Fi bug report. That includes a debug profile that you can install. I recommend that you follow those instructions and, the next time you see the problem, capture the resulting logging and attach that to your bug.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"