Open
Bug 1469679
Opened 7 years ago
Updated 1 year ago
Blocklisted addons cause sync to create an error log: Failed to apply incoming record Error: Add-on not found after install
Categories
(Firefox :: Sync, defect, P3)
Firefox
Sync
Tracking
()
NEW
People
(Reporter: wtds.trabalho, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(10 files)
65.09 KB,
application/gzip
|
Details | |
1.19 MB,
text/plain
|
Details | |
4.81 MB,
text/plain
|
Details | |
5.37 MB,
application/x-bzip
|
Details | |
3.60 MB,
application/x-bzip
|
Details | |
767.95 KB,
application/x-bzip
|
Details | |
242.86 KB,
application/x-bzip
|
Details | |
30.29 KB,
text/plain
|
Details | |
28.33 KB,
text/plain
|
Details | |
42.44 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180619102337
Steps to reproduce:
After start with clean profile(Trying to solve problems...) I can't sync anything anymore...
I got a error with addon sync, "mini vid" extension, maybe experimental test pilot from the past.
But clean profile don't have addons installed.
Actual results:
Nothing syncing(whitout history, addons, password :-( sad...)
The error (Many times, linux terminal):
1529438638604 Sync.AddonUtils INFO Found 0 / 1 add-ons during repository search.
1529438638604 Sync.Engine.Addons.Store WARN Failed to apply incoming record {a13e95f2-1743-4f74-a4fb-cbb7dafbf94a}: Error: Add-on not found after install: @min-vid (resource://services-sync/engines/addons.js:335:13) JS Stack trace: create@addons.js:335:13
async*applyIncoming@engines.js:350:13
async*applyIncoming@addons.js:300:11
async*applyIncomingBatch@engines.js:315:15
async*_applyRecords@engines.js:1415:29
async*_processIncoming@engines.js:1296:33
async*_sync@engines.js:1837:13
async*WrappedNotify@util.js:179:27
async*sync@engines.js:900:12
async*_syncEngine@enginesync.js:214:13
async*sync@enginesync.js:156:21
async*onNotify@service.js:1131:13
async*WrappedNotify@util.js:179:27
async*WrappedLock@util.js:135:22
async*_lockedSync@service.js:1124:12
async*sync/<@service.js:1116:13
async*WrappedCatch@util.js:105:22
async*sync@service.js:1105:12
async*syncIfMPUnlocked/<@policies.js:541:7
Crash report not generated.. (Why not?)
Expected results:
No errors and sync working...
Trying to help with sync test...
Thanks!
Comment 1•7 years ago
|
||
Please enter about:sync-log into the address bar and attach the latest log.
Flags: needinfo?(wtds.trabalho)
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to Gingerbread Man from comment #1)
> Please enter about:sync-log into the address bar and attach the latest log.
Hi,
I will attach examples of my error logs.
Thanks
Reporter | ||
Comment 4•7 years ago
|
||
Reporter | ||
Comment 5•7 years ago
|
||
Reporter | ||
Comment 6•7 years ago
|
||
Reporter | ||
Comment 7•7 years ago
|
||
Reporter | ||
Comment 8•7 years ago
|
||
Reporter | ||
Comment 9•7 years ago
|
||
Updated•7 years ago
|
Component: Untriaged → Firefox Sync: Backend
Product: Firefox → Cloud Services
Updated•7 years ago
|
Flags: needinfo?(markh)
Comment 10•7 years ago
|
||
I'm afraid none of the logs you uploaded have the reported error "Error: Add-on not found after install: @min-vid"
Flags: needinfo?(markh) → needinfo?(wtds.trabalho)
Reporter | ||
Comment 11•7 years ago
|
||
(In reply to Mark Hammond [:markh] from comment #10)
> I'm afraid none of the logs you uploaded have the reported error "Error:
> Add-on not found after install: @min-vid"
Sorry, I got more examples.
From log:
1536007465584 Sync.Engine.Addons.Store WARN Failed to apply incoming record {dce71e0b-0432-4151-a5b2-ff0dcef99483}: Error: Add-on not found after install: contact@web-security.com(resource://services-sync/engines/addons.js:341:13) JS Stack trace: create@addons.js:341:13
async*update@addons.js:376:13
async*applyIncoming@engines.js:353:13
async*applyIncoming@addons.js:306:11
async*applyIncomingBatch@engines.js:316:15
async*_applyRecords@engines.js:1411:29
async*_processIncoming@engines.js:1292:33
async*_sync@engines.js:1835:13
async*WrappedNotify@util.js:179:27
async*sync@engines.js:895:12
async*_syncEngine@enginesync.js:214:13
async*sync@enginesync.js:156:21
async*onNotify@service.js:1139:13
async*WrappedNotify@util.js:179:27
async*WrappedLock@util.js:135:22
async*_lockedSync@service.js:1132:12
async*sync/<@service.js:1124:13
async*WrappedCatch@util.js:105:22
async*sync@service.js:1113:12
async*syncIfMPUnlocked/<@policies.js:537:7
Can I help you in the search of origin?
Thanks
Flags: needinfo?(wtds.trabalho) → needinfo?(markh)
Reporter | ||
Comment 12•7 years ago
|
||
Reporter | ||
Comment 13•7 years ago
|
||
Reporter | ||
Comment 14•7 years ago
|
||
Comment 15•7 years ago
|
||
I found https://www.web-security.com/how-to-install/, which offers a .xpi file and also points to https://addons.mozilla.org/de/firefox/addon/web-security/ to get it on addons.mozilla.org - however, that latter page shows an error. addons.mozilla.org doesn't host an addon with this ID at all.
What is your history with this addon? Is it possible you installed it from addons.mozilla.org, but it was then taken down from addons.mozilla.org? I think that would explain the error you are seeing.
Flags: needinfo?(markh) → needinfo?(wtds.trabalho)
Reporter | ||
Comment 16•7 years ago
|
||
I remenber me installed this addon in the past.
I heard about mozilla team found addons for security with problems and remove in the running browsers.
Is that maybe related? Or I'm I've removed the addon from another client.
By the way sometimes I got errors related of that. Can the sync fix these type of problem by yourself? Because in this case I can't do anything. Can I?
(Learning English...)
Thanks!
Flags: needinfo?(markh)
Reporter | ||
Comment 17•7 years ago
|
||
How about the removal of the item from the origin after certain number of tries?
1535060765698 Sync.Engine.Addons.Store WARN Failed to apply incoming record {dce71e0b-0432-4151-a5b2-ff0dcef99483}: Error: Add-on not found after install: contact@web-security.com(resource://services-sync/engines/addons.js:341:13) JS Stack trace: create@addons.js:341:13
Thanks!
Reporter | ||
Comment 18•7 years ago
|
||
Please see:
https://tecnoblog.net/256255/mozilla-complementos-firefox-usuarios/
https://www.bleepingcomputer.com/news/security/mozilla-removes-23-firefox-add-ons-that-snooped-on-users/
The Mozilla removed the addon and after this action my sync not work anymore.
I thinks sync fix for this case is recommended.
https://tecnoblog.net/wp-content/uploads/2018/08/WebSecurity-removed-700x255.png
https://www.bleepstatic.com/content/posts/2018/08/16/WebSecurity-removed.png
Flags: needinfo?(rob)
Reporter | ||
Comment 19•7 years ago
|
||
Hi,
Please see: https://bugzilla.mozilla.org/show_bug.cgi?id=1483995
Is the add-on sync problem a consequence of the Bug 1483995?
Thanks
Comment 20•7 years ago
|
||
Thanks for the report and sleuthing.
The error message "Add-on not found after install: [guid of blocklisted addon]" looks like an accurate description of the situation. Indeed, the add-on GUIDs from this bug are from add-ons that are blocklisted (https://wiki.mozilla.org/Blocklisting).
This (client) logic needs to be fixed to account for blocklisted add-ons (don't fail hard):
https://searchfox.org/mozilla-central/rev/a41fd8cb947266ea2e3f463fc6e31c88bfab9d41/services/sync/modules/engines/addons.js#313-341
If this bug report is true, then it means that many users who had installed a blocklisted add-on cannot sync. That sounds like a pretty bad bug, and if possible a backend fix would be nice (e.g. by serving an empty dummy add-on via sync).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(rob)
Priority: -- → P1
Comment 21•7 years ago
|
||
Thanks for digging in!
Sync works fine, it just creates an error log as it fails to handle a single addon - all other addons and all other engines work fine. The only fix I think Sync should make here would be to not create an error log, but that's not a high priority as the user typically never sees any indication of this error.
Component: Firefox Sync: Backend → Sync
Flags: needinfo?(wtds.trabalho)
Flags: needinfo?(markh)
Priority: P1 → --
Product: Cloud Services → Firefox
Summary: Sync.Engine.Addons.Store - Failed to apply incoming record Error: Add-on not found after install: @min-vid → Blocklisted addons cause sync to create an error log: Failed to apply incoming record Error: Add-on not found after install
Updated•7 years ago
|
Priority: -- → P3
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•