On 1.1 e.me still uses an old api key which needs to be replaced.
Created attachment 795983 [details] Patch - redirect to github PR
Attachment #795983 - Flags: review?(crdlc)
Comment on attachment 795983 [details] Patch - redirect to github PR ok
Attachment #795983 - Flags: review?(crdlc) → review+
merged into master 1c50003a83a3bea05f763e627a07b3cadca03a9a https://github.com/mozilla-b2g/gaia/commit/1c50003a83a3bea05f763e627a07b3cadca03a9a
Leo+ as it cuts access off with old api key.
blocking-b2g: leo? → leo+
uplifted to 1.1 e0d2ebba786a7ea4ea88c11da5ffa7309ebee544 https://github.com/mozilla-b2g/gaia/commit/e0d2ebba786a7ea4ea88c11da5ffa7309ebee544
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
status-b2g-v1.1hd: --- → fixed
Verified fixed on Leo Build ID: 20130905041201 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/c5937a004145 Gaia: 2529db165272ac53bfcb3b426be884e4e86dde89 Platform Version: 18.1 Looking into the file on the build we flashed, we are able to see Api key: 65106dbdb655b25f2defa18ab7d1ecd8 We are not sure if there is anything else to check besides making sure the key is the same on the build we flash.
status-b2g18: fixed → verified
That's actually all that's needed Jeni, thanks! For extra verification you can make sure the API key works - simply perform e.me related action (opening a collection, searching, etc.). If the API key is valid - you should get results.
You need to log in before you can comment on or make changes to this bug.