Musicbee Traceback from error on load

[wysocki]

Whenever I load my webpage from my Galaxy S5, I get the attached Exception report in the log. Even with the messages, everything appears to be working ok. What causes that traceback report? It doesn't come up when I load the page from a pc.

[Pako]

What browser do you use on your mobile?
When I will be able to reproduce this error, I'll be able to fix it somehow.
Meanwhile, you can try using a different browser. I can recommend, for example, CM Browser. That seems to be pretty good.

Pako

[wysocki]

Very odd. I've been using Dolphin as my browser. The error message actually comes up when I exit the browser AFTER being on my webserver/index.html page. It happens if my defalt webpage is Musicbee or if my homepage contains Musicbee in an iframe. I've installed CM as you suggested and it behaves exactly the same way as Dolphin. I start the browser to its default page, browse to my webserver, hit "back" to go back to the default page, hit back again to close the browser (or just select "Exit" in the browser), then the error appears.

Interestingly, Chrome browser does not have any problems! (just shows "closing" in the log upon exit).
Musicbee was setup from your installation zip from Dec 26, 2015.

[Pako]

Please try a modified version of Webserver plugin:

__init__.py

Webserver - version 3.10

(192.64 KiB) Downloaded 250 times

Pako

[wysocki]

Sorry, didn't fix the problem, this time it was expecting a string but found an integer! I tried multiple phones and multiple computers with the same results. Chrome browser had no problems. A few times I got Firefox on the computers to cause the problem when I closed the tab or browser, but I could not determine a consistent pattern. On the phones, Dolphin and CM Browser were similar: both created the error when the tab was closed and/or the browser was closed although CM allowed me to navigate to another url, then close the browser with no error. Dolphin would always error on close if it had ever loaded musicbee. (Note: The 'Websocket closing: "/x03/xe9"' message was caused whenever a browser was closed without the error. )

[Pako]

Sorry, didn't fix the problem, this time it was expecting a string but found an integer!

It's my fault. Please try corrected version.
The problem is that I can not reproduce it.

(Note: The 'Websocket closing: "/x03/xe9"' message was caused whenever a browser was closed without the error. )

That is correct.
That means "endpoint is going down".
I did revamped to make it "human readable".

Pako

[wysocki]

Perfect! Thanks for handling this so quickly, it's a great plugin - and thanks for introducing me to Musicbee!