Shizuku Play Store Compatibility Issue on Android 17: What We Know

Some Android 17 users may see Shizuku missing from Google Play search or marked unavailable for their device. That does not mean Shizuku has been removed from Google Play, and it does not prove that every Android 17 device is incompatible.

As of September 7, 2026, Shizuku’s public Google Play listing is still live. It shows more than 10 million downloads and remains accessible through a web browser. Google Play lists March 10, 2024 as its last update date.

The newer concern comes from an Android 17 device report filed in Shizuku’s official GitHub repository.

What Was Reported on Android 17?

On September 2, 2026, a Shizuku GitHub issue was opened for a Pixel 11 Pro running Android 17.

The report says Shizuku was hidden from normal Play Store search on that device. When the listing was reached another way, Google Play displayed a message saying the app was “made for an older version of Android.” The device compatibility view also marked it as not working on that phone.

The report identified:

This is a real report in the official RikkaApps/Shizuku repository, but it remains a user-submitted issue. The issue page currently shows no assignee, linked pull request, or developer explanation identifying the cause.

Current Status: Confirmed vs Unconfirmed

The distinction matters. A device-specific Play Store compatibility result is not the same thing as a worldwide app removal.

Why Can Shizuku Exist on the Web but Be Unavailable on a Phone?

Google Play can keep an app’s public product page accessible while restricting whether a particular device or user can install it. That is why both of these can be true at the same time:

• Shizuku’s public Google Play page is available.
• A particular Android 17 device may be told that the app is unavailable or incompatible.

Google Play considers app and device compatibility when deciding whether an application should be available to a user. Target API requirements can also affect discoverability on newer Android versions.

This became especially relevant on August 31, 2026.

Google now requires existing mobile apps to target Android 15 / API level 35 or higher to remain available to new users whose devices run Android versions newer than the app’s target API. Apps targeting API 34 or lower can lose availability for those newer-device users.

That rule is relevant to the timing of the Shizuku report, but there is not enough evidence to say it caused this specific problem.

The Target SDK Clue Does Not Prove the Cause

Shizuku’s current source code on the official RikkaApps GitHub repository sets:

• compileSdk = 36
• targetSdk = 36
• minSdk = 24

A target SDK of 36 is above Google Play’s current API 35 availability threshold for existing mobile apps.

There is one catch: the current GitHub source is not automatically the same build currently distributed through Google Play.

The public Play listing says it was last updated on March 10, 2024, while the official GitHub release page now marks v13.6.0 as the latest release. A separate recent GitHub report also asks the developers to update Google Play because, according to that user, Play is still serving v13.5.4 while GitHub has v13.6.0. That is another user report rather than a developer statement, but it supports checking the Play Store build separately from the current GitHub code.

Until RikkaApps or Google identifies the reason, the safest conclusion is:

There is evidence of a Play Store compatibility/availability problem on at least one Android 17 device, but the exact cause has not been confirmed.

Does This Mean Shizuku Itself Does Not Work on Android 17?

No. A Google Play availability warning and Shizuku’s behavior after installation are two different questions.

Google Play decides whether an app can be discovered or installed on a device. Runtime problems happen after the app is installed and involve a different set of Android changes.

There are separate Android 17 reports in the Shizuku repository involving managed or authorized apps, but those should not be used as proof that the Play Store issue has the same cause.

For the broader compatibility picture, see Shizuku on Android 17: What Works Now. That page covers Android 17 behavior without turning this Play Store report into a general Android 17 guide.

What Should You Do If Google Play Says Shizuku Is Incompatible?

First, identify which problem you actually have.

If Shizuku is only missing from Play Store search or Google Play says it was made for an older Android version, treat that as a store availability issue. It does not by itself prove that the installed Shizuku service cannot run.

If Shizuku is already installed and working on your phone, the Play Store warning alone is not evidence that you need to remove it.

If you need the current installer, use a source that clearly identifies the package, version and origin rather than downloading a random file that claims to bypass Android 17 restrictions.

For an actual Android 17 runtime problem—rather than Play Store availability—use the Android 17 compatibility page linked above.

Is Shizuku Removed From the Play Store?

No global removal has been confirmed.

The current Google Play web listing remains available and identifies the app as Shizuku by Xingchen & Rikka.

The Android 17 report concerns how Google Play treats Shizuku on an affected device. Calling that a Play Store removal would go beyond the evidence.

Is Every Android 17 Device Affected?

There is no evidence supporting that claim.

Issue #2422 documents a Pixel 11 Pro case. Other Android 17 issues exist in the Shizuku repository on devices including Pixel models, but those reports describe different runtime problems rather than the same Play Store availability warning.

Device, Android build, Play Store distribution rules and the Shizuku build being served can all matter. A result on one phone should not be presented as universal Android 17 behavior.

Has RikkaApps Confirmed a Fix?

Not for this Play Store report at the time of this check.

Issue #2422 remains open and currently shows no assignee, development branch or linked pull request.

The official GitHub release page still identifies v13.6.0 as the latest release. Its release notes include Android 16 QPR1 support, but they do not provide an official explanation for the Android 17 Play Store warning described in issue #2422.

This page should be updated when RikkaApps, Google Play, or a new official Shizuku release provides evidence that changes the status.