After upgrade version 2.2 not connection from mopidy mobile


#21

It’s alright :slight_smile:
It is a real pity. The app is great.
Perhaps it will fix it.


#22

@kingosticks FWIW, saving the following to a local file and opening (read “Ctrl-O”) in Firefox 62.0.3 seems to result in

Origin: null

to be sent. Yes, that’s the string “null”, AFAICS.

<script src="http://localhost:6680/mopidy/mopidy.js"></script>
<script>
  var mopidy = new Mopidy({
    webSocketUrl: "ws://localhost:6680/mopidy/ws/"
  });
  mopidy.connect();
</script>

Addendum: Chromium Version 69.0.3497.81 (Official Build), running on Ubuntu 18.04 (64-bit) when opening the same file also sends

Origin: file://

so this doesn’t seem to be Cordova-only thing.


#23

@Feryy: I am quite confident that we will come up with a solution for Mopidy v2.2.1 pretty soon.

Otherwise, with Mopidy Mobile being installed on 2,300 “active devices” (according to Google), I’d better mute my Inbox NOW…


#24

I’ve created some issues and a PR for the websocket side of things.



#25

Great, and thanks for working night shifts for this :grinning:


#26

Mopidy 2.2.1 with the fixes discussed here is now out: https://docs.mopidy.com/en/latest/changelog/#v2-2-1-2018-10-15