Some Pixel owners are reporting My Pixel app missing tabs today, with the entire bottom navigation bar gone and no way to reach Support or the Google Store within the app. At least one affected user saw a pop-up just before the tabs vanished: "Support and Google Store features are not available in your region. You can manage your orders and repairs on the Google Store website." They dismissed it, and the navigation bar disappeared.
The warning matches My Pixel's regional eligibility message, the one the app shows when a device doesn't qualify for the full experience. That suggests the gating system may be involved. Whether it's misfiring, correcting an earlier misconfiguration, or doing something intentional is not established. Google has not commented.
Why the My Pixel app bottom bar disappeared for some users
My Pixel's bottom bar carries four tabs: Home, Tips, Support, and Store. For affected users, all four are gone. Support and Store are unreachable within the app; the warning message redirects users to the Google Store website instead. Several Pixel owners on Reddit have independently confirmed the same behavior, though the specific regions, device models, and app versions involved haven't been established.
Tips is worth addressing separately. It predates the My Pixel rebrand; it was already part of the original Pixel Tips app. When Google rebranded as My Pixel in August 2025, the tabs tied to regional eligibility were specifically Support and Store. At launch, the newer region-gated additions were Support and Store, while Tips carried over from the original app. Tips disappearing alongside the newer tabs appears to be a side effect of the entire bottom bar collapsing, not a targeted restriction on Tips specifically.
This is also distinct from My Pixel's standard regional tiering. Since launch, users outside supported markets have received the redesigned interface and new name, but not the Support or Store tabs. That's a static condition built into how the app was designed. What's reported now is different: users who had the full experience have lost it. A fixed geographic limit doesn't produce that sequence.
How My Pixel's regional eligibility system works
When Google rebranded Pixel Tips as My Pixel in August 2025, Support and Store were restricted to five markets with specific language requirements: Australia, the United Kingdom, and the United States in English only; Japan in Japanese only; Taiwan in Mandarin only. A device in a covered country but set to an unsupported language would still be gated out. Everyone else got the new name and redesigned interface, nothing more.
Later in 2025, Google quietly extended full access to six additional countries: India in English, Canada in English and French, Germany in German, France in French, Italy in Italian, and Spain in Spanish. The change was spotted through an update to the Play Store listing, not through any announcement from Google.
The granular country-and-language pairing wasn't incidental. A user in Germany with their device set to English would be gated out just as firmly as a user in a country that was never on the list. The eligibility check runs against both variables, which matters when trying to understand why tabs might disappear for someone who shouldn't be affected.
Pixel features are routinely activated through backend switches that operate independently of system or app updates. Users can wait several weeks after a Pixel Drop before individual features appear, because Google controls them server-side on its own schedule. The same infrastructure that quietly extended access last December could, in principle, narrow it the same way, without any signal to users that it's happening.
What the region message may indicate about the Google Pixel My Pixel app issue
When a user saw the unavailability warning just before the tabs disappeared, the sequence suggests the app's regional eligibility check may have been involved. That warning is consistent with the message My Pixel shows when a device doesn't meet regional requirements. That it appeared immediately before the tabs vanished points toward an eligibility determination rather than a display glitch, though the research doesn't confirm the underlying mechanism definitively.
Three scenarios could produce this outcome. If affected users are in countries never on the supported list, the most straightforward read is that eligibility was briefly misconfigured to grant access it wasn't meant to, and the system has since corrected itself. If users in confirmed supported markets like the US, UK, or India are losing tabs, that suggests the eligibility check is misfiring, possibly misreading a device's region or language setting. And if the tabs return without any Play Store update or user action, that may suggest the issue resolved server-side, which is how the December 2025 expansion was handled.
From a user's perspective, a deliberate rollback and an eligibility misfiring produce identical results: tabs gone, region message, no explanation. That's a direct consequence of managing feature availability through backend switches with no user-facing change log. Only Google can tell the difference between a mistake and a decision.
What affected users can try
The most targeted first step is checking the device region and language settings. My Pixel's eligibility logic operates at the country-and-language level, meaning an unsupported language variant could trigger a gating decision even for a device in a covered market. A US Pixel set to British English is an edge case, but the system's granularity makes it worth ruling out before assuming the access loss is permanent.
Signing out of the Google account tied to the Pixel and signing back in may prompt the app to re-run its eligibility check against the current backend state. Clearing My Pixel's app data and relaunching is a low-effort additional step. Neither has been confirmed as a reliable fix, but neither requires anything that can't be undone.
Waiting is also a legitimate option. The December 2025 expansion arrived with no announcement and no app version change. If the tabs return without any Play Store update, that would confirm the issue was always server-side, and resolved itself the same way it appeared. Affected users outside clearly supported markets may be waiting for a backend correction rather than anything they can initiate themselves.
What happens now
Several key details remain unresolved: which specific markets are affected, which device models, and which app versions. The scale of the issue hasn't been established. Google has not commented.
The most useful signal to watch for is whether reports surface from users in confirmed supported markets, specifically the US, UK, India, or the six countries added last December. If they do, that rules out the "correcting an earlier mistake" explanation and points more clearly toward a misfiring eligibility check. A quiet update to the Play Store listing is also worth monitoring. That's the same mechanism that signaled the December expansion, and it wouldn't require an app update on users' devices.
For anyone not currently affected, the broader pattern is still worth understanding. My Pixel's eligibility system can make features appear and disappear without any app update, silently, on Google's schedule, with no user-facing explanation. The current reports make that unusually visible: a region message appeared, tabs disappeared, and users are left to infer what changed and why. Whether this turns out to be a misconfiguration or something more deliberate, the mechanism responsible is the same one governing access for everyone using the app.
Comments
Be the first, drop a comment!