# Our Android-compatible extension does not show up in search on FF for Android. Why?

**URL:** <https://discourse.mozilla.org/t/our-android-compatible-extension-does-not-show-up-in-search-on-ff-for-android-why/126069>\
**Category:** Firefox for Android Add-ons\
**Tags:** issue\
**Created:** [January 11, 2024, 10:59pm UTC](https://discourse.mozilla.org/t/our-android-compatible-extension-does-not-show-up-in-search-on-ff-for-android-why/126069 "2024-01-11T22:59:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![IllogicalRobot](https://avatars.discourse-cdn.com/v4/letter/i/5f8ce5/32.png) [@IllogicalRobot](https://discourse.mozilla.org/u/IllogicalRobot)\
**Post date:** [January 11, 2024, 10:59pm UTC](https://discourse.mozilla.org/t/our-android-compatible-extension-does-not-show-up-in-search-on-ff-for-android-why/126069/1 "2024-01-11T22:59:56Z")

</div>

Hello,

We have an extension available here [Toolbox for Google Play Store™ – Get this Extension for 🦊 Firefox (en-US)](https://addons.mozilla.org/en-US/firefox/addon/toolbox-google-play-store/) and installable on both desktop and Android.

However, in FF for Android, it doesn’t come up in search [Search results for "Toolbox" – Add-ons for Firefox Android (en-US)](https://addons.mozilla.org/en-US/android/search/?q=Toolbox).

 ![image](https://us1.discourse-cdn.com/flex001/uploads/mozilla/original/3X/4/1/41a92d5190b477e330333979c4834a54a59b79f3.png)

I can’t figure out why this is happening. There’s no toggle to publish/unpublish from Android specifically anywhere in the backend that I have been able to find. It’s clearly compatible as it installs on Android and works fine. So why is it not in search?

Thank you.

---

<div class="post-metadata">

**Author:** ![Edward\_Sullivan](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/edward_sullivan/32/63229_2.png) [@Edward\_Sullivan](https://discourse.mozilla.org/u/Edward_Sullivan)\
**Post date:** [January 12, 2024, 5:58pm UTC](https://discourse.mozilla.org/t/our-android-compatible-extension-does-not-show-up-in-search-on-ff-for-android-why/126069/2 "2024-01-12T17:58:24Z")

</div>

Hey @IllogicalRobot.

I am not seeing your extension as Android compatible per: [https://addons.mozilla.org/en-US/android/addon/toolbox-google-play-store/](https://addons.mozilla.org/en-US/android/addon/toolbox-google-play-store/). I assume that is why it is not getting returned.

I believe you would have to submit another version and mark it as Android compatible during the submission workflow.

@dotproto can you check me on the above pls?

---

<div class="post-metadata">

**Author:** ![pmarks](https://avatars.discourse-cdn.com/v4/letter/p/ecccb3/32.png) [@pmarks](https://discourse.mozilla.org/u/pmarks)\
**Post date:** [January 12, 2024, 8:50pm UTC](https://discourse.mozilla.org/t/our-android-compatible-extension-does-not-show-up-in-search-on-ff-for-android-why/126069/3 "2024-01-12T20:50:14Z")

</div>

Excerpt from your `manifest-firefox.json`:

```
"browser_specific_settings": {
	"gecko": {
		"id": "{f7e00fda-62e6-4361-8450-a335408e1efe}"
	}
},

```

You will need to add a `gecko_android` section. Also I notice that `manifest.json` and `manifest-firefox.json` have different contents. Does Firefox actually read the latter? I can’t find any mention of `manifest-firefox.json` in the docs.

---

<div class="post-metadata">

**Author:** ![dotproto](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/dotproto/32/62957_2.png) [@dotproto](https://discourse.mozilla.org/u/dotproto)\
**Post date:** [January 17, 2024, 7:32pm UTC](https://discourse.mozilla.org/t/our-android-compatible-extension-does-not-show-up-in-search-on-ff-for-android-why/126069/4 "2024-01-17T19:32:49Z")

</div>

> [@Edward\_Sullivan](#):
>
> I believe you would have to submit another version and mark it as Android compatible during the submission workflow.
> 
> @dotproto can you check me on the above pls?

Yep, [declaring the extension is Android-compatible in manifest.json](https://extensionworkshop.com/documentation/publish/version-compatibility/#browser-specific-settings) is our recommended approach. That said, developers can also use [AMO’s compatibility settings](https://extensionworkshop.com/documentation/publish/version-compatibility/#amo-compatibility) to adjust the visibility of an extension after publishing. See also the [recommendations](https://extensionworkshop.com/documentation/publish/version-compatibility/#recommendations) section of that page.

> [@pmarks](#):
>
> `manifest-firefox.json` in the docs.

No, Firefox does not read `manifest-firefox.json`.

---

<div class="post-metadata">

**Author:** ![IllogicalRobot](https://avatars.discourse-cdn.com/v4/letter/i/5f8ce5/32.png) [@IllogicalRobot](https://discourse.mozilla.org/u/IllogicalRobot)\
**Post date:** [January 25, 2024, 10:32pm UTC](https://discourse.mozilla.org/t/our-android-compatible-extension-does-not-show-up-in-search-on-ff-for-android-why/126069/5 "2024-01-25T22:32:10Z")

</div>

Thank you, everyone. To clarify, manifest-firefox.json is in the source but we manually copy it to manifest.json, if I’m not mistaken, when we release for Firefox, especially since our Chrome version has now moved to manifest v3.

Thanks for the `gecko_android` tip, I haven’t seen it before, this must be it.