On my Flame device with FirefoxOS Nightly, launching the client tells me "Sorry, your device isn't compatible with this app". This is the marketplace version of the Firefox Hello client which https://hello.firefox.com/<room-id> redirected me to when trying to join a room.
After some looking around, it seems the version I'm running (marketplace version, so I guess the unmodified production version?) only has "ALCATELOneTouch6015X" in the devices list of compatibility.json and no "Mozilla" item (this makes sense with the productionconfiguration).
Now after following MDN's Flame update guide (flashing the base image and activating the nightly updates), FirefoxOS Nightly's UA string is Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0. I understand this can be changed back to "Mozilla/5.0 (Mobile; ALCATELOneTouch4012X; rv:40.0) Gecko/40.0 Firefox/40.0" by setting the general.useragent.device_id pref, but as things are now the compatibility check fails here.
Problem
On my Flame device with FirefoxOS Nightly, launching the client tells me "Sorry, your device isn't compatible with this app". This is the marketplace version of the Firefox Hello client which
https://hello.firefox.com/<room-id>
redirected me to when trying to join a room.After some looking around, it seems the version I'm running (marketplace version, so I guess the unmodified production version?) only has
"ALCATELOneTouch6015X"
in thedevices
list of compatibility.json and no"Mozilla"
item (this makes sense with the production configuration).Now after following MDN's Flame update guide (flashing the base image and activating the nightly updates), FirefoxOS Nightly's UA string is
Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
. I understand this can be changed back to"Mozilla/5.0 (Mobile; ALCATELOneTouch4012X; rv:40.0) Gecko/40.0 Firefox/40.0"
by setting thegeneral.useragent.device_id
pref, but as things are now the compatibility check fails here.Solutions?
Can you detect you're on a Flame device without asking FFOS Nightly users to add
"ALCATELOneTouch6015X"
to their UA string? (also since MDN mentions Mozilla discourages using device-specific UA strings)