👍
--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/25411fb5-6ee7-46a7-b346-83f08cb38048n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAOG_JKJ1QVtfuYGx3Zn8TcHTtczBmeO%2B%2BK%2B%3DeLjqRvKs0%3Dd-%3Dw%40mail.gmail.com.
It seems that all users bookmark IDs are periodically changing. In my extension, users reports for example, the app was originally linked to a folder with ID 183, but after Chrome updates, it crashes because the ID of this folder has changed to 93.
Hi Oliver,
When I mentioned a crash, I was referring to an exception in the extension that occurs when it tries to access a bookmark category by an ID that no longer exists.
This issue occurs not because the user manually deleted the category, but because the ID of the category has changed.
For example:
Other bookmarks -> extension_folder -> some bookmarks / folders
In the extension, I store the ID of extension_folder and also the IDs of some bookmarks / folders. However, after some time, the extension stops being able to correctly access extension_folder or some bookmarks / folders because the ID of extension_folder or any other folder changes.
I have a workaround where I locate the folder for my extension by its “title” and restore the relations using the new IDs, but this approach is not practical for long-term development. Users are still experiencing instability in the extension.
I can add logging on my side to gather more information when an ID mismatch occurs, which might help us better understand at what stage or how often this happens.
I’ve written a detailed investigation on this bug today in the Chromium issues.
In the next few days, I’ll add a metric to my extension to track how many users are affected and to monitor when the fix is implemented to ensure it works.