Remove the BLOCKED_PERMISSIONS from the AddonManager
Categories
(Firefox for Android :: WebExtensions, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox122 | --- | verified |
People
(Reporter: amejia, Assigned: willdurand)
References
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
More context can be found below:
https://github.com/mozilla-mobile/firefox-android/pull/4568#discussion_r1407723934
Updated•2 years ago
|
Comment 1•2 years ago
|
||
The check is not strictly necessary. See my comments at bug 1759601.
| Assignee | ||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Authored by https://github.com/willdurand
https://github.com/mozilla-mobile/firefox-android/commit/439e2f88092aaf3035f9d1b48ea54ed9c41f0172
[main] Bug 1867297 - Remove the use of BLOCKED_PERMISSIONS
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
Hey Alex, could you please verify this bug?
Comment 5•2 years ago
|
||
Verified as Fixed. Tested on the latest Nightly for Android (122.0a1/Build #2015990855, fab78e74bf+, GV: 122.0a1-20231210093611).
To verify the fix, I created a custom collection with Video DownloadHelper (which requires the nativeMessaging permission) and attempted to install the add-on on both the latest Beta (which does not have the fix) and the latest Nightly (which has the fix). According to https://bugzilla.mozilla.org/show_bug.cgi?id=1759601#c3 , the add-on should fail to install on Beta but succeed on Nightly, which is what happens, confirming the fix.
Moreover, about:debugging on Nightly shows a log stating addons.webextension.{b9db16a4-6edc-47ec-a1f4-b86292ed211d} WARN Loading extension '{b9db16a4-6edc-47ec-a1f4-b86292ed211d}': Reading manifest: Invalid extension permission: nativeMessaging when installing the add-on.
Compared to the add-on installed on Desktop, the permissions tab for the add-on on Android also does not show/mention the “Exchange messages with programs other than Firefox”, which is the nativeMessaging permission.
Considering the above, the issue is fixed.
Description
•