Bug 1986027 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Inspired by Alexander's post, I stepped through the code when manually checking for updates. My test profile is on 144, with my own add-on incompatible and disabled. I then updated ATN to mark it compatible with 144.* and checked for updates. Nothing.

The url which was queried was

> https://versioncheck.addons.thunderbird.net/update/VersionCheck.php?reqVersion=2&id={8845E3B3-E8FB-40E2-95E9-EC40294818C4}&version=6.4&maxAppVersion=143.*&status=userEnabled,incompatible&appID={3550f703-e582-4d05-9a08-453d09bdfdc6}&appVersion=144.0.1&appOS=Linux&appABI=x86_64-gcc3&locale=de&currentAppVersion=144.0.1&updateType=97&compatMode=strict

Removing the compatMode does return something:

> https://versioncheck.addons.thunderbird.net/update/VersionCheck.php?reqVersion=2&id={8845E3B3-E8FB-40E2-95E9-EC40294818C4}&version=6.4&maxAppVersion=143.*&status=userEnabled,incompatible&appID={3550f703-e582-4d05-9a08-453d09bdfdc6}&appVersion=144.0.1&appOS=Linux&appABI=x86_64-gcc3&locale=de&currentAppVersion=144.0.1&updateType=97

And indeed, toggling `extensions.strictCompatibility` off, updated the compat data and re-enabled my add-on. Can you or your users reproduce this?
Revision 1 by
on 
Inspired by Alexander's post, I stepped through the code when manually checking for updates. My test profile is on 144, with my own add-on incompatible and disabled. I then updated ATN to mark it compatible with 144.* and checked for updates. Nothing.

The url which was queried was

> https://versioncheck.addons.thunderbird.net/update/VersionCheck.php?reqVersion=2&id={8845E3B3-E8FB-40E2-95E9-EC40294818C4}&version=6.4&maxAppVersion=143.*&status=userEnabled,incompatible&appID={3550f703-e582-4d05-9a08-453d09bdfdc6}&appVersion=144.0.1&appOS=Linux&appABI=x86_64-gcc3&locale=de&currentAppVersion=144.0.1&updateType=97&compatMode=strict

Removing the compatMode does return something:

> https://versioncheck.addons.thunderbird.net/update/VersionCheck.php?reqVersion=2&id={8845E3B3-E8FB-40E2-95E9-EC40294818C4}&version=6.4&maxAppVersion=143.*&status=userEnabled,incompatible&appID={3550f703-e582-4d05-9a08-453d09bdfdc6}&appVersion=144.0.1&appOS=Linux&appABI=x86_64-gcc3&locale=de&currentAppVersion=144.0.1&updateType=97

And indeed, toggling `extensions.strictCompatibility` off, updated the compat data and re-enabled my add-on. Can you or your users reproduce this?

Edit: A couple of minutes later, the url with `compatMode=strict` also returned something, so this seems to be a caching issue? I will retry.
Revision 2 by
on 
Inspired by Alexander's post, I stepped through the code when manually checking for updates. My test profile is on 144, with my own add-on incompatible and disabled. I then updated ATN to mark it compatible with 144.* and checked for updates. Nothing.

The url which was queried was

> https://versioncheck.addons.thunderbird.net/update/VersionCheck.php?reqVersion=2&id={8845E3B3-E8FB-40E2-95E9-EC40294818C4}&version=6.4&maxAppVersion=143.*&status=userEnabled,incompatible&appID={3550f703-e582-4d05-9a08-453d09bdfdc6}&appVersion=144.0.1&appOS=Linux&appABI=x86_64-gcc3&locale=de&currentAppVersion=144.0.1&updateType=97&compatMode=strict

Removing the compatMode does return something:

> https://versioncheck.addons.thunderbird.net/update/VersionCheck.php?reqVersion=2&id={8845E3B3-E8FB-40E2-95E9-EC40294818C4}&version=6.4&maxAppVersion=143.*&status=userEnabled,incompatible&appID={3550f703-e582-4d05-9a08-453d09bdfdc6}&appVersion=144.0.1&appOS=Linux&appABI=x86_64-gcc3&locale=de&currentAppVersion=144.0.1&updateType=97

And indeed, toggling `extensions.strictCompatibility` off, updated the compat data and re-enabled my add-on. Can you or your users reproduce this?

**Edit: A couple of minutes later, the url with `compatMode=strict` also returned something, so this seems to be a caching issue? I will retry.**

Back to Bug 1986027 Comment 5