Closed
Bug 1000277
Opened 11 years ago
Closed 11 years ago
[e.me] [Tarako] New API key for Tarako
Categories
(Firefox OS Graveyard :: Gaia::Everything.me, defect)
Tracking
(blocking-b2g:1.3T+, b2g-v1.3T fixed)
People
(Reporter: ranbena, Assigned: amirn)
Details
Attachments
(1 file)
In order to enable Tarako specific search results, the devices need to identify themselves upon communication with the e.me API server.
Plz add dm to clientInfo
If we're to ship w/ e.me; I think the e.me folks need this so they can make improvements specific to tarako...
blocking-b2g: --- → 1.3T?
status-b2g-v1.3T:
--- → affected
|
||
Comment 2•11 years ago
|
||
triage: 1.3T+ to enable tarako with e.me
hi Ran, do you mind taking this bug? thanks
blocking-b2g: 1.3T? → 1.3T+
Flags: needinfo?(ran)
|
Reporter | |
Comment 3•11 years ago
|
||
We're not yet sure that this is the way to go. It depends on the implementation on the server side which is still in debate.
Flags: needinfo?(ran)
|
|
Reporter | |
Comment 5•11 years ago
|
||
It's related but I was referring to an internal debate in EverythingMe.
I will have an answer to this soon.
Flags: needinfo?(ran)
|
Assignee | |
Comment 7•11 years ago
|
||
we already send out osVersion and deviceType with every request to E.me API
(e.g., unagi with a master build reports "osVersion": "1.5.0.0-prerelease", "deviceType":"unagi1")
changing scope of this bug to replace the api key.
Summary: [e.me] Send device model on every API request → [e.me] [Tarako] New API key for Tarako
|
|
Assignee | |
Comment 8•11 years ago
|
||
Attachment #8415205 -
Flags: feedback?(ran)
|
|
Assignee | |
Updated•11 years ago
|
Assignee: nobody → amirn
|
|
Reporter | |
Updated•11 years ago
|
Attachment #8415205 -
Flags: feedback?(ran) → feedback+
|
||
Updated•11 years ago
|
blocking-b2g: 1.3T? → 1.3T+
|
|
Assignee | |
Comment 9•11 years ago
|
||
landed in 1.3t: https://github.com/mozilla-b2g/gaia/commit/9716b7b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
|
||
Updated•11 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•