While creating a test case for this bug, I saw that even the expected case (update rendered an add-on incompatible) is not causing the add-on to update. STR: - fresh TB78 profile - install https://addons.thunderbird.net/thunderbird/downloads/file/1018660/quicktext-3.6-tb.xpi - update the profile to TB91 - add-on is correctly marked as incompatible, but not updated, user has to manually search for updates (this is what the startupChanges check should take care off). What this bug is actually about is to update add-ons if there is a new version available for the new platform. Consider v1.0: https://github.com/jobisoft/github-based-release-example/blob/versions/bug1738458/1.0/manifest.json v1.1: https://github.com/jobisoft/github-based-release-example/blob/versions/bug1738458/1.1/manifest.json v1.1 might use new API feature introduced in TB91 or v1.0 may in fact be incompatible with TB91, as some API could have been deprecated. When updating to TB91, version v1.1 should be automatically installed. Removing the check for startupChanges (which do not seem to work anymore) fixes both.
Bug 1738458 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
While creating a test case for this bug, I saw that even the expected case (update rendered an add-on incompatible) is not causing the add-on to update. STR: - fresh TB78 profile - install https://addons.thunderbird.net/thunderbird/downloads/file/1018660/quicktext-3.6-tb.xpi - update the profile to TB91 - add-on is correctly marked as incompatible, but not updated, user has to manually search for updates (this is what the startupChanges check should take care off). What this bug is actually about is to update add-ons if there is a new version available for the new platform, even if the current installed version is not defined incompatible. Consider v1.0: https://github.com/jobisoft/github-based-release-example/blob/versions/bug1738458/1.0/manifest.json v1.1: https://github.com/jobisoft/github-based-release-example/blob/versions/bug1738458/1.1/manifest.json v1.1 might use new API feature introduced in TB91 or v1.0 may in fact be incompatible with TB91, as some API could have been deprecated. When updating to TB91, version v1.1 should be automatically installed. Removing the check for startupChanges (which do not seem to work anymore) fixes both.
While creating a test case for this bug, I saw that even the expected case (update rendered an add-on incompatible) is not causing the add-on to update. STR: - fresh TB78 profile - install https://addons.thunderbird.net/thunderbird/downloads/file/1018660/quicktext-3.6-tb.xpi - update the profile to TB91 - add-on is correctly marked as incompatible, but not updated, user has to manually search for updates (this is what the startupChanges check should take care off). What this bug is actually about is to update add-ons if there is a new version available for the new platform, even if the current installed version is not defined incompatible. Consider v1.0: https://github.com/jobisoft/github-based-release-example/blob/versions/bug1738458/1.0/manifest.json v1.1: https://github.com/jobisoft/github-based-release-example/blob/versions/bug1738458/1.1/manifest.json v1.1 might use new API feature introduced in TB91 or v1.0 may in fact be incompatible with TB91, as some API could have been deprecated. When updating to TB91, version v1.1 should be automatically installed. Removing the check for startupChanges (which does not seem to work anymore) fixes both.