Closed Bug 1075159 Opened 10 years ago Closed 7 years ago

[B2G] In release builds, assert MLS API key is set

Categories

(Core :: DOM: Geolocation, defect)

Product:
Core
Component:
DOM: Geolocation
Platform:
x86
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- disabled
b2g-v2.0M --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: garvan, Unassigned)

References

Details

B2G devices have been shipped with the MLS API key not set. We should somehow assert on release builds that the key is set to a real key (not just no-mozilla-api-key).
[Blocking Requested - why for this release]: We should really try to fix this in B2G 2.1 (Gecko 34). This should be a simple code change, but it would prevent the recurrence of configuration problems in partners' device builds. The motivating factor is that Dolphin devices in the field are using a default null API key instead of the MLS API key we gave SPRD. This could have been a major problem for geolocation on Dolphin, but we worked around the problem on the server for now.
Blocks: geo-b2g-2.1
blocking-b2g: --- → 2.1?
status-b2g-v1.4: --- → affected
status-b2g-v2.0: --- → disabled
status-b2g-v2.0M: --- → affected
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → affected
This change would be nice to have, but it is not a blocker.
blocking-b2g: 2.1? → ---
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.