Closed
Bug 946808
Opened 11 years ago
Closed 11 years ago
The user will notice that region will show up as Worldwide on MP Stage
Categories
(Marketplace Graveyard :: Consumer Pages, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: vikas.nanda, Unassigned)
References
Details
Attachments
(1 file)
14.62 KB,
image/png
|
Details |
Region code:Crow, Plomassy and Hanger Device:Unagi white Connection:3g/wifi Phone number/MSISDN:0175 6980737 Carrier:n/a Last 4 digits CC:n/a Test App used:n/a steps to reproduce: 1. Start mp stage 2. Select settings expected behavior: The region should automatically be set based on the country the user is in. observed behavior: The region is displayed as worldwide.
Comment 1•11 years ago
|
||
You will need to submit logs for this issue for us to debug further: https://github.com/mozilla/ashes#submitting-logs > The region should automatically be set based on the country the user is in. This depends on many things. If you do not have a recognized SIM card in the device, the region will be set by GeoIP. If GeoIP fails to detect a known region, you will be placed in the worldwide region. Note also that geoip tends to be wrong if the user is near a cultural border. This issue is tracked in bug 941939.
Updated•11 years ago
|
Flags: needinfo?(vikas.nanda)
Comment 2•11 years ago
|
||
Also, where do you live?
Reporter | ||
Comment 3•11 years ago
|
||
Hi Matt & Cvan Ashes log ID 6b994 Note that this has only just started occurring for us in all 3 countries we are testing in. I am using a Telekom de sim card. I am testing in Wiesbaden, Germany
Flags: needinfo?(vikas.nanda)
Reporter | ||
Comment 4•11 years ago
|
||
Also note that I am having to use the debug menu to manually select the region I am testing in.
Comment 5•11 years ago
|
||
Your logs show the following: [mobilenetwork][detectMobileNetwork] navigator.mozMobileConnection unavailable They also show that you're visiting the site with the URL `marketplace.allizom.org/?carrier=telefonica`. This information means you are not visiting the Marketplace via the app. You will not be geolocated via SIM if you visit via the browser, since the browser has no access to the SIM card. Additionally, we do not assign you a region based on your carrier (some carriers span multiple regions). It's curious that you are not getting a region via geoip. I'll take a closer look at this in a minute.
Comment 6•11 years ago
|
||
https://github.com/mozilla/fireplace/commit/e2a4680e0b2abcd616ccdea53cf4584574da79ea This should fix the issue. I'll ask cvan to push stage so this can be verified.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•11 years ago
|
||
The region is still showing up as worldwide in all the countries we are currently testing in.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 8•11 years ago
|
||
Please submit logs. https://github.com/mozilla/ashes#submitting-logs
Flags: needinfo?(vikas.nanda)
Comment 9•11 years ago
|
||
basta, is there a chance that this issue is happening on stage since it is a hosted app? I remember hosted apps having issues with mnc/mcc detection. Although geoip should work.
Comment 10•11 years ago
|
||
Oh, yeah, that could be the case. If it's not wrapped in a packaged app like Yule Log there is no SIM card detection whatsoever. I'm more concerned with the lack of geoip, though, which wouldn't be affected by being in a hosted app. The logs should show what's up with that.
Comment 12•11 years ago
|
||
The logs show that there was no sim and the API did not provide a region from geoip. The behavior here is expected given the circumstances. I've filed an API bug to expose what's going on with geoip under the hood. Right now it's not clear if there is an error, you're being geolocated incorrectly, or if there's a bug that's preventing geoip from happening.
Comment 13•11 years ago
|
||
It looks like this was also fixed by https://github.com/mozilla/fireplace/commit/27a905fc1674266151fca02c3763a22e45e15088
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•