It's a feature (joking). Must of the time rebooting will fix the issue. Seems like sometimes hardware layer and app api stop to communicate and the NEHotspotNetwork seems have very big flows in callback handling. You can have same issues in any of the calls based on NEHotspotNetwork may be they will fix that part but i would not count on it too much.

Honestly i find this behaviour as many others completely non-sense.... But since we have to comply.... You have to tell to yourself the mantra "this is the best way to proceed" lool.