Why Can't I Find My Flutter App on Google Play After Publishing? 7 Causes and Checks (2026)
Why can’t I find my Flutter app on Google Play after publishing?
Most of the time the app is not actually public yet: it is still in review, approved but held by managed publishing, or released to a testing track instead of production. If it is public, it may be hidden from your device by country targeting or device filters, or from new users on newer Android versions by an old target API level. And if none of that applies, Google Play search may simply not rank it yet for its own name. Each cause has a quick check in Play Console. This guide lists the seven in the order I check them on my own apps, with the fix for each.
The 60-second check: open the listing by package name
Before anything else, open https://play.google.com/store/apps/details?id= followed by your application ID (the applicationId in android/app/build.gradle, for example com.example.myapp). Google’s Play Console Help gives the same route from inside the console: select the app, then click View on Google Play under its name.
- The page loads for you: the app is published. Skip to causes 4 to 7.
- “Item not found” or nothing loads: it is not public yet, or not available to your account or country. Start with causes 1 to 3.
The seven causes at a glance
| # | Cause | Where to check | Fix |
|---|---|---|---|
| 1 | Still in review | Publishing overview, app status | Wait; extended reviews can take 7 days or longer |
| 2 | Approved but held by managed publishing | Publishing overview | Click Publish changes |
| 3 | Released to a testing track, not production | Test and release, Production | Create a production release (closed test first for new personal accounts) |
| 4 | Not available in your country | Production, Countries / regions | Add the country |
| 5 | Your device is filtered out | Device catalog | Review minSdk, required features and excluded devices |
| 6 | Target API level too old for new users | App bundle explorer, target SDK | Raise targetSdkVersion and ship an update |
| 7 | Search has not ranked it yet | Play Store search vs direct link | Give it time; improve the store listing |
1. The app is still in review
Play Console shows an app status and an update status under the app’s name. Google’s publishing status page warns that for certain developer accounts reviews take longer, “up to seven days or longer in exceptional cases.” First apps from new accounts often fall into that group. If the status still says in review, there is nothing to fix yet; note the date you submitted and check the status once a day.
2. It was approved, but managed publishing is holding it
With managed publishing turned on, approved changes wait until you publish them. The same Google page explains that “after it’s approved, you control exactly when the changes are published.” It is easy to forget you enabled it months ago. Open Publishing overview: if changes are ready to publish, publish them.
3. You released to a testing track, not production
Google’s visibility help is direct: “If you want your app to be available and searchable on Google Play, make sure that your app is published to production.” Internal, closed and open testing tracks are not the same as a public release; internal and closed tests are only reachable by invited testers. On a personal developer account created after 13 November 2023, production is locked until a closed test with at least 12 testers opted in for 14 continuous days; our guide to the 12-testers, 14-days closed testing rule walks through it. Once production is live, a staged rollout controls update percentages for existing users; a first release goes to everyone in the selected countries.
4. It is not available in your country
Countries are chosen per release in Play Console. The Android developers page on Google Play filters says the app “will then be available to users in only the countries you select.” A first release that targets only one market is invisible everywhere else, including to you when travelling or behind a VPN. Google also advises against adding your own geolocation or IP restrictions inside the app, because they push some users to proxies and can get purchases flagged.
5. Your device is filtered out
Google Play compares each device with what your app declares. Per the same filters page, if a device does not match, Play “hides your application from search results and category browsing, even if a user specifically requests the app” by its direct link. For Flutter apps the usual suspects are:
- minSdkVersion above the test phone’s Android version.
- Required hardware features added by a plugin, such as a camera feature declared as required instead of optional.
- ABI filters that leave out the device’s CPU architecture.
- Excluded devices in the device catalog, sometimes set long ago.
Play Console’s device catalog shows whether a specific model is supported and why not.
6. The target API level is too old for new users
This one catches older apps rather than new ones. Google’s target API page states that from 31 August 2026 existing apps must target Android 15 (API level 35) or higher “to remain available to new users on devices running Android OS higher than your app’s target API level.” An app targeting API 34 or lower is only offered to devices running that Android version or lower. Existing installs keep working, which is why the problem can go unnoticed. Raise targetSdkVersion in Gradle and ship an update; our notes on the target API 36 deadline and extension cover the plugin upgrades that usually come with it.
7. Search has not ranked it yet
If the direct link works on your device but searching the exact name does not find it, the app is live and the issue is search. Google’s help notes that Play search weighs factors such as app titles, developer names and descriptions, and that results vary by device, location and carrier. In the Play developer community, a common report is that a brand-new app can be found by its package ID before it appears for its name. A distinctive title, a clear short description and your developer name in searches all help; ranking for generic words takes much longer.
My order of checks
- Open the direct link in a desktop browser while signed out, and on a phone.
- Read the app status and update status in Play Console.
- Check Publishing overview for held changes.
- Confirm a production release exists, with the right countries.
- Look up your test phone in the device catalog.
- Check the target SDK of the live bundle.
- Only then worry about search ranking.
I build and ship Flutter and Firebase apps at GSPTeck, and this list comes from releasing them; the apps themselves are on the GSPTeck homepage.
FAQ
How long until a new app appears on Google Play?
After approval it is live at once in the selected countries, but review itself can take up to seven days or longer for some accounts, and search can lag behind the direct link.
Why can I open my app’s link but not find it in search?
The app is published; Play search simply does not rank it yet. Search for the exact name plus your developer name, and give the listing time.
Why do some phones not show my app at all?
Device filters such as minSdk, required features or excluded devices hide the app on unsupported phones, even from direct links. Check the device catalog.
Does an old target API remove my app from Google Play?
No, but new users on Android versions newer than your target cannot install it. Existing users keep it.
Sources
- Play Console Help: app visibility and discovery issues (checked 2026-10-22)
- Play Console Help: publishing status and managed publishing (checked 2026-10-22)
- Android Developers: filters on Google Play (checked 2026-10-22)
- Play Console Help: target API level requirements (checked 2026-10-22)