Bad init about q-municate-web HOT 7 CLOSED

Hi, @ajthinking
Can you give us an error from console? Is error only on FF browser?

from q-municate-web.

There is no error in the console. The last three rows output are posted above which shows App did init (!). Its not only FF, also chrome latest versions. Addons disabled, popups allowed etc so all should be good on that side.

Usually I would expect the next messages to follow:
[ServiceProxy] Response: Object
QB SDK: Users is found Object
etc but they do not show up even though the app should have initiated.

Checking the network tab gives no clues (all 200's).
So somewhere it is stopping the unwrapping of the app and Im stranded at the preloader screen. I cant find why/where it is stopping. Maybe check where SDK or App would output "[ServiceProxy] Response: Object" ? Thats would be the next log message.

from q-municate-web.

I think that the problem may be with old data, which need for autologin. Qmunicate save some data in browser's localStorage to use them later. Try to clear local/session storage, cookie and other cache. Or may be you have had a critiacal error when connected to chat and qmunicate did relaod page in this case; so you can turn on "preserve log" to see what have happened before reloading.

from q-municate-web.

So I did localStorage.clear(), empty cache and all other site specific data with no effect.
Preserving the log does not show any signs of reloading either.

from q-municate-web.

Can you reproduse this error when you develop on https://localhost:{PORT} (using command "grunt serve")? Or is this error just on your host server?

from q-municate-web.

Error was totally on my side, bad cache combined with html edits. Closing this. Thanks for the support!

from q-municate-web.

Thanks for response! Have a good day!

from q-municate-web.