Edge storage.sync.set broken
See original GitHub issueError: Could not complete the operation due to error 8e5e05e2.
The error:
- Is completely undocumented
- Only appears when packaged as an appx
I thought this was only happening because something wasn’t provisioned for us on MSFT’s side, guess I was wrong.
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18493567/
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
IE/Edge can't sync local-storage data · Issue #110 - GitHub
Description Hi when listen data-changed from app-localstorage-document, it is not changed data of the tag or event. IE11/Edge were not set ...
Read more >Fix OneDrive sync problems - Microsoft Support
Learn how to fix common OneDrive personal or OneDrive for Business sync problems. ... If you see this icon, it means your OneDrive...
Read more >Common Microsoft Edge Problems, and How to Fix Them
Browsers read and write to your local hard drive or SSD, and un-optimized storage can slow you down. Go into File Explorer, right-click...
Read more >Algorithm to break down item for chrome storage sync
I am trying to save a string (correction: it is an object containing multiple strings of varying sizes) using chrome.storage.sync.set but am ...
Read more >How to Properly Set Up your Chrome Storage Sync
Setting up Chrome Storage Sync for a cloud backup is not difficult. ... troubles fixing an error, your system may be partially broken....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mymindstorm: Thanks. I mostly left a note here because your issue is one of the top hits for this error message.
The “Extension ID” is “EdgeExtension_” + the package family name; the prefix adds 14 characters which pushes your extension’s ID out to 66 characters, just over the limit. Unfortunately, there’s no workaround short of re-releasing the extension with a shorter name.
I’ve reached out to the documentation team to ask them to document this bug, and to the partner onboarding team to help them reject any proposed listing with an ID that exceeds the limit.
You’re correct in noting that the Chromium-based Edge will not suffer from this problem, but the old EdgeHTML-based version of Edge will be with us for quite some time.
Closing as edge is being replaced with chromium Edge.