the connecting spinner didnt stop when reconnected the internet. What should I do

I've seen this before for certain cases of reconnection where there's a race condition in how the notification events are dispatched and handled.

This is all reworked in the upcoming 3.1.x codebase, so while it might still be present (I'm not entirely sure it's fixed, but I haven't been able to recreate it yet), it's a big untangle for 3.0.x so I will likely not fix it in 3.0.x.