Error 8 in the NEHotspotConfigurationError domain is .internal, aka NEHotspotConfigurationErrorInternal. This error typically indicates that something went wrong in some sort of expected way, but we decided not to surface the exact cause [1]. This has come up a bunch of times before on the forums, and I have various titbits to share.
To start, I want to address some specific cases:
- You’ll see this error if your app isn’t signed with the
com.apple.developer.networking.HotspotConfigurationentitlement. To fix this, use Xcode’s Signing & Capabilities editor to add the Hotspot capability to your app. - Historically developers reported a situation where once they encountered the error it would show up consistently, but then it would go away on restarting the device. If you see behaviour like that, that’s definitely a bug and I encourage you to file it as such. I have more about filing such bugs in Filing a Wi-Fi Bug Report. Of course, you have to wait to reproduce the error again before you’ll be able to file that bug, because the act of restarting cleared the issue.
- I’ve seen reports where such problems only occur on a specific type of device, for example, on iPhone 16 but not on earlier or later iPhones. That’s definitely something that Apple should investigate, and I recommend that you file a bug about it.
- If the problem is being reported by your users but you can’t reproduce it yourself, consider the various suggestions in Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem.
Assuming you’re still here (-: the next step is to determine whether the problem is specific to NEHotspotConfigurationManager or not. Try joining the accessory’s network from Settings > Wi-Fi. Does that also have problems?
If so, that’s not something we can help you with here on the forums. The focus of the Apple Developer Forums is primarily to help developers with the APIs in Apple’s various platform SDKs [2]. We’re not set up to help accessory developers with Wi-Fi issues. However, there are still things you can do, as I explain in Filing a Wi-Fi Bug Report.
At this point you have an error that:
- Persists across restarts
- Happens with all Apple devices
- You can reproduce
- Only affects
NEHotspotConfigurationManager
If that’s correct then there are a couple of things you might look at:
- Coerce the error to an
NSErrorand print that. Does it reveal anything interesting? - Also check the underlying error property (
NSUnderlyingErrorKey) for hints. - When reproducing the error, monitor the system log for log entries in the
com.apple.networkextensionsubsystem. Do those offer any clues?
Note For lots of hints and tips about the system log, see Your Friend the System Log.
And finally, if you have questions about this case, feel free to start a thread here on the forums and we’ll try to help you out. Put it in the App & System Services > Networking subtopic and tag it with Network Extension.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] There’s also the .unknown error. See this post for a brief summary of the difference.
[2] And with Apple tools and some developer-oriented services.
Revision History
- 2026-03-18 Added a missing entitlement bullet to the specific case list.
- 2026-03-17 First posted.