addonRepository returns emtpy array for rtamo
Categories
(WebExtensions :: General, defect)
Tracking
(firefox66+ verified, firefox67 verified)
People
(Reporter: mixedpuppy, Assigned: mixedpuppy)
References
Details
Attachments
(1 file)
|
47 bytes,
text/x-phabricator-request
|
lizzard
:
approval-mozilla-beta+
|
Details | Review |
It turns out the kill switch id we use results in an empty array returned from AddonRepository due to the id we send being different from what we get back[1].
Alternate fixes:
- Wait for 67: switch back to Fetch
- but make sure there is one central implementation
- make sure there are no hard coded urls as before
- Get it into 66: AMO returns the id it received
In the second case this could be handled outside firefox. Looking over the code, nothing in AddonRepository (result from getAddonsByIDs) uses the id beyond the filter mentioned. ActivityStream also does not use the id[2].
[1] https://searchfox.org/mozilla-central/rev/dbddac86aadf1d4871fb350bbe66db43728a9f81/toolkit/mozapps/extensions/internal/AddonRepository.jsm#469
[2] https://searchfox.org/mozilla-central/rev/dbddac86aadf1d4871fb350bbe66db43728a9f81/browser/components/newtab/lib/OnboardingMessageProvider.jsm#207
| Assignee | ||
Comment 1•6 years ago
|
||
We could also (if delaying till 67) fix AddonRepository to recognize the rta id.
Comment 2•6 years ago
|
||
CCing Stuart and Mat for visibility on the AMO side.
Comment 3•6 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #1)
We could also (if delaying till 67) fix AddonRepository to recognize the rta id.
If this is the only blocker and rtamo is otherwise ready for 66, this would probably be a small enough change to uplift to beta.
Comment 4•6 years ago
|
||
FWIW I would largely prefer not adding a hack to AMO for this.
Comment 5•6 years ago
|
||
(In reply to Mathieu Pillard [:mat] from comment #4)
FWIW I would largely prefer not adding a hack to AMO for this.
I second this, and if an uplift for 66 is possible that sounds like the best solution to me.
| Assignee | ||
Comment 6•6 years ago
|
||
AddonRepository validates IDs that are returned from AMO. We
need to handle the case where we are using rta prefix for ReturnToAMO.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 7•6 years ago
|
||
I've also manually verified the fix against a download on windows, about:welcome shows me tabby cat!
| Assignee | ||
Comment 8•6 years ago
|
||
Updated•6 years ago
|
| Assignee | ||
Comment 10•6 years ago
|
||
Comment on attachment 9047102 [details]
Bug 1530816 support RTA IDs in AddonRepository
Beta/Release Uplift Approval Request
- Feature/Bug causing the regression: None
- User impact if declined: addon recommendations cannot be provided.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: QE has test plans for the entire RTAMO flow.
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Limited to AMO api use. Tests coverage is good on this.
- String changes made/needed: none
Comment 11•6 years ago
|
||
Comment on attachment 9047102 [details]
Bug 1530816 support RTA IDs in AddonRepository
Support for testing return to AMO.
OK for uplift for beta 12.
Comment 12•6 years ago
|
||
| bugherder | ||
Comment 13•6 years ago
|
||
Verified using the above build for Fx67 using multiple white listed extensions including tabby cat, everything appears fine using this version. Tests were run using Windows 10 x64.
Comment 14•6 years ago
|
||
| bugherder uplift | ||
Comment 15•6 years ago
|
||
Verified using Firefox 66.0 (20190307095232) on Windows 10 x64 bit. Testing has been done in the same way as on Fx67, no issues have occurred with either white listed or non white listed addons.
Description
•