NEHotspotConfiguration *hotspotConfig = [[NEHotspotConfiguration alloc] initWithSSID:ssid passphrase:psk isWEP:NO];
[[NEHotspotConfigurationManager sharedManager] applyConfiguration:hotspotConfig completionHandler:^(NSError * _Nullable error) {
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.
so we're not checking it
I recommend that you do. If the probability is about 10%, you’ll need at most 50 manual tests to confirm whether this is an API issue or not. That’s probably less than an hour’s work. Or you could automate it with an Xcode UI test.
Anyway, the reason why I ask is because, if the problem reproduces in Settings, you know that your code is correct, in which case the next step is to file a bug report. And that brings me to this:
Can you process this order number FB16819345
I had a look at that bug and it’s on its way back to you with a request for more info. When filing a bug report about Wi-Fi, it’s vital that you include a sysdiagnose log taken shortly after reproducing the problem. Better yet, follow the Wi-Fi for iOS/iPadOS instructions on our Bug Reporting > Profiles and Logs page.
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Error 11 in the NEHotspotConfigurationErrorDomain domain is NEHotspotConfigurationErrorUnknown, which isn’t at all helpful.
If you attempt to join the network using Settings > Wi-Fi, does that work?
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.
so we're not checking it
I recommend that you do. If the probability is about 10%, you’ll need at most 50 manual tests to confirm whether this is an API issue or not. That’s probably less than an hour’s work. Or you could automate it with an Xcode UI test.
Anyway, the reason why I ask is because, if the problem reproduces in Settings, you know that your code is correct, in which case the next step is to file a bug report. And that brings me to this:
Can you process this order number FB16819345
I had a look at that bug and it’s on its way back to you with a request for more info. When filing a bug report about Wi-Fi, it’s vital that you include a sysdiagnose log taken shortly after reproducing the problem. Better yet, follow the Wi-Fi for iOS/iPadOS instructions on our Bug Reporting > Profiles and Logs page.
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Thanks!
Could you please continue to investigate the issue of being unable to join the network?
Me personally? No. But your bug will be looked at by the Wi-Fi engineering team.
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Dear Apple Developer Team,
Could you please take a look at the issue where WiFi is still unable to join networks even after updating to the latest iOS 18.4 (22E239) version? This issue has already been submitted as feedback (FB17013980 - iOS 18.4 (22E239) WiFi - Unable to Join Network). We would appreciate your assistance in following up on this matter.
Thank you!
As I mentioned above, I’m not in a position to debug Wi-Fi on-the-wire compatibility problems for you. The best way to escalate such issues is to file an actionable bug report.
Speaking of actionable bug reports,
follow the on our page.
A number of your bugs are coming back to you because you didn’t provide those diagnostic logs. I recommend that you correct that.
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Dear Apple Engineer,
We have reproduced this issue again. The "Unable to Join Network" problem has been reported under FB16988773 (WIFI - Unable to Join Network), and it occurs on iPhone 13 running iOS 18.5.
Could you please help escalate this to the Wi-Fi analysis team for further investigation?
Thank you very much for your support.
Could you please help escalate this … ?
I’ve checked that your bug has landed in the right place; it’s now up to the Wi-Fi team to investigate.
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Dear Apple Engineer,
Thank you for your previous reply and support.
We have followed the instructions and submitted the necessary information/logs via Feedback Assistant (FB16988773 (WIFI - Unable to Join Network)). However, we haven't received any further updates so far.
This issue is impacting our users in production, and we would greatly appreciate it if your team could help escalate and prioritize the investigation.
Please kindly let us know if there’s anything else we can provide to assist.
Thank you again for your support!
Best regards
we would greatly appreciate it if your team could help escalate and prioritize the investigation.
I’m sorry but I’m not able to do this. Apple’s R&D engineering teams prioritise bugs based on the many competing demands on their time.
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
We would appreciate it if you could let us know the expected response time
I’m sorry but I’m neither capable of, nor allow to, make such predictions. See tip 3 in Quinn’s Top Ten DevForums Tips.
Share and Enjoy
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the
Apple Developer Forums Participation Agreement and Apple provided code is subject to the
Apple Sample Code License.
