Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add-on with gecko_android: {} in manifest is not marked as Android-compatible by AMO #9423

Closed
Rob--W opened this issue Jan 15, 2024 · 5 comments

Comments

@Rob--W
Copy link
Member

Rob--W commented Jan 15, 2024

I have an add-on on AMO, marked with browser_specific_settings.gecko_android: {}, uploaded to AMO on July 2nd, 2023 and approved quickly (Rob--W/dont-track-me-google@db36130)

The add-on is however not marked as compatible with Firefox for Android: https://addons.mozilla.org/en-US/android/addon/dont-track-me-google1

As the developer, I can edit the version and manually add compatibility, but before touching anything at all, I wonder whether there is a bug on AMO that we need to fix.

Potentially relevant information: I unchecked the "Compatible with Android" option in march 2021 because the add-on suddenly started to appear in the search results without users being able to install it (#14058). It seems that every version uploaded since (version 4.24) does not have the compatibility set. This despite (latest) version 4.26 containing gecko_android in its manifest.json file.

I would expect any add-on with gecko_android: {} set to be Android-compatible, unless compatibility is explicitly disabled for that specific version.

┆Issue is synchronized with this Jira Task

@diox
Copy link
Member

diox commented Jan 16, 2024

This is weird.

Setting gecko_android: {} should indeed opt you in Android compatibility, and in fact should be impossible to remove. That was added in AMO before submission of the latest version, so it should have worked.

Do you remember how that version was submitted ? (Devhub, old submission API, new submission API)

@Rob--W
Copy link
Member Author

Rob--W commented Jan 16, 2024

I submitted through the devhub.

@Rob--W
Copy link
Member Author

Rob--W commented Jan 25, 2024

Is there anything to investigate, or should I just fix the metadata manually (as a developer) and close this issue?

@diox
Copy link
Member

diox commented Feb 5, 2024

Sorry for the delay, I think this it caused by a weird combination of being recommended for Firefox but not Android and using that property that has since been fixed. Please fix manually and re-open if you don't automatically get Android compatibility next time you upload a version, regardless of the method.

@KevinMind
Copy link
Contributor

@KevinMind KevinMind transferred this issue from mozilla/addons-server May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants