"Developer verification" is required to install apk. (Future) Solutions

[Figim]

According to new rules, only apps from verified developers can now be installed
"Android developer verification" is intended for applications outside the "Play Store". Free and $25 account options. Will be free for hobbyists

Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices.

Or you need to register to share outside the Play Store

We will need such applications to install our applications. We can install other applications with adb without "developer verification"

https://developer.android.com/developer-verification/guides/faq

Registration for apps outside the Play Store

https://developer.android.com/developer-verification/guides/android-developer-console

[ainaracatgirl]

This is not true. You can go to developer settings on your phone and disable app verification over USB/ADB. Then install InstallWithOptions via ADB and use it normally.

Will Android Debug Bridge (ADB) install work without registration? As a developer, you are free to install apps without verification with ADB. This is designed to support developers' need to develop, test apps that are not intended or not yet ready to distribute to the wider consumer population. Last updated: Sept 3, 2025

[Figim]

This is not true. You can go to developer settings on your phone and disable app verification over USB/ADB. Then install InstallWithOptions via ADB and use it normally.

Will Android Debug Bridge (ADB) install work without registration? As a developer, you are free to install apps without verification with ADB. This is designed to support developers' need to develop, test apps that are not intended or not yet ready to distribute to the wider consumer population. Last updated: Sept 3, 2025

But how do we install the "InstallWithOption" application? (if the developer is not approved )

[ainaracatgirl]

This is not true. You can go to developer settings on your phone and disable app verification over USB/ADB. Then install InstallWithOptions via ADB and use it normally.

Will Android Debug Bridge (ADB) install work without registration? As a developer, you are free to install apps without verification with ADB. This is designed to support developers' need to develop, test apps that are not intended or not yet ready to distribute to the wider consumer population. Last updated: Sept 3, 2025

But how do we install the "InstallWithOption" application? (if the developer is not approved )

You go to developer settings, disable app verification over USB/ADB, and install it via ADB with a computer.

[Figim]

This is not true. You can go to developer settings on your phone and disable app verification over USB/ADB. Then install InstallWithOptions via ADB and use it normally.

Will Android Debug Bridge (ADB) install work without registration? As a developer, you are free to install apps without verification with ADB. This is designed to support developers' need to develop, test apps that are not intended or not yet ready to distribute to the wider consumer population. Last updated: Sept 3, 2025

But how do we install the "InstallWithOption" application? (if the developer is not approved )

You go to developer settings, disable app verification over USB/ADB, and install it via ADB with a computer.

Also google will maybe add a popup to accept or decline this

[zacharee]

I'm going to register IWO once the verification feature is available.

[Figim]

I'm going to register IWO once the verification feature is available.

Shizuku is not updated on the playstore. The last update was in 2024. I wonder if it will be updated? 😏

RikkaApps/Shizuku#1431

[CharaDreemurrDT]

This is not true. You can go to developer settings on your phone and disable app verification over USB/ADB. Then install InstallWithOptions via ADB and use it normally.

Will Android Debug Bridge (ADB) install work without registration? As a developer, you are free to install apps without verification with ADB. This is designed to support developers' need to develop, test apps that are not intended or not yet ready to distribute to the wider consumer population. Last updated: Sept 3, 2025

It could be also possible to use Shizuku and Termux together to install the APK. I think it would be just using adb install on Termux using Shizuku, but I don't really know.

[Figim]

This is not true. You can go to developer settings on your phone and disable app verification over USB/ADB. Then install InstallWithOptions via ADB and use it normally.

Will Android Debug Bridge (ADB) install work without registration? As a developer, you are free to install apps without verification with ADB. This is designed to support developers' need to develop, test apps that are not intended or not yet ready to distribute to the wider consumer population. Last updated: Sept 3, 2025

It could be also possible to use Shizuku and Termux together to install the APK. I think it would be just using adb install on Termux using Shizuku, but I don't really know.

Termux does not support shizuku

[ainaracatgirl]

Yes it does, via the rish shell.

[TotallyAvailable]

Also don't forget to think ahead slightly more given how aggressive of a move this really is...now they can conveniently terminate anyone and all their registered apps if they violate their (probably soon to exist) "verified developers agree to not provide tools to bypass restrictions in place to verify device integrity" rule.

Given that there are already certain rules in place to keep non-pro users in the Play Store ecosystem...the moment you can conveniently bypass the entire verification process by just using a free app (even like signing apps on device) on the play store ? ban hammer drop ? or them backtracking on that "promise" on allowing the ADB bypass.

Also how would the entire system even work with 100s of millions of devices that won't receive any more updates anyway. (Besides a massive mintargetSDK push/enforcement which is already happening with Chrome/Webview currently)

Also the "registering" part...how many different users can register the same packageID under their name and how could that possibly not go wrong.

While it is great that there are already quite a few potential options available...we are also giving Google all that time until enforcement day to find ways to block every single one of them without (too) obviously violating existing "law".

And all of this still leaves out the damage already done to apps that were never on (or (mainly) made for) the Play Store...

[Figim]

Also don't forget to think ahead slightly more given how aggressive of a move this really is...now they can conveniently terminate anyone and all their registered apps if they violate their (probably soon to exist) "verified developers agree to not provide tools to bypass restrictions in place to verify device integrity" rule.

Given that there are already certain rules in place to keep non-pro users in the Play Store ecosystem...the moment you can conveniently bypass the entire verification process by just using a free app (even like signing apps on device) on the play store ? ban hammer drop ? or them backtracking on that "promise" on allowing the ADB bypass.

Also how would the entire system even work with 100s of millions of devices that won't receive any more updates anyway. (Besides a massive mintargetSDK push/enforcement which is already happening with Chrome/Webview currently)

Also the "registering" part...how many different users can register the same packageID under their name and how could that possibly not go wrong.

While it is great that there are already quite a few potential options available...we are also giving Google all that time until enforcement day to find ways to block every single one of them without (too) obviously violating existing "law".

And all of this still leaves out the damage already done to apps that were never on (or (mainly) made for) the Play Store...

ADB install will not be canceled. Use adb as a power user and they don't override it. And if they did, Android developers would completely lose out, because it wouldn't be any different from iOS. Actually, anyone who uses adb knows what they are doing. Google is actually doing the right thing. Millions of viral mods were spreading more easily across devices

Shizuku etc can be installed using ADB, if it is not available in the Play Store. Then install everything with Shizuku

There will be no "package name" issue when using ADB. Google has announced this themselves and using adb means there will be no issue. When using ADB, you will install the application in a simple way, just like now. "Package name" is required for "developer verification"

[TotallyAvailable]

Just too bad that WE (the power users) won't be able to even sustain all the devs/apps with legitimate reasons not to register. Remember that all those (now forced to) DO NOT have to follow Play Store/Google "guidelines" currently...

I totally get the idea (without needing to fully agree) BUT this is the end of OUR freedom...I could care more or less as power user that's "fine" BUT it is already happening exactly as predicted...just look at Steam or you know...the entire US right now. Voted a certain way in the past ? sucks for you, no verified status. Certain dating apps ? "Doesn't align with our values" - Gone. Emulators ? Big N (you know the one) says no -> Gone. Signal refusing a backdoor in the future ? Gone. Critical journalism from any agency not inline with the current government (anywhere) ? Gone (extending world wide of course, just look over that big body of water (either direction) for more examples)
Any perfectly legal App from a dev based in country A causing "inconvenience" in country B ? Just went from Google saying "how is that my problem ?" to (the likely convenient option) "Gone" given that they know everything about you and the value you provide them on top of literally being the reason they introduce this verification system...this wasn't a thing before outside of Play Protect flagging..."Don't be evil" now has full control over billions of devices they literally do not own.

Hopefully WE get the idea (this isn't about attacking anyone not agreeing with my opinions...like the number one mistake we keep repeating). This is purely based on understanding the history of my country...not to look away in a situation like this. (Silence until there's no one left to speak out for you)

If 99% of your X thousand/million users are now no longer existent due to the removal of your verified status & including all your other Apps (= requiring ADB install and thanks to Play App Signing a fresh one even)...your app(s) is/are dead - you either bend over and eat it up(=comply) or effectively disappear.

And that's it from me on my "concern" regarding this topic. Very sorry on even having to mention political issues (and guaranteed abuse) at all...should ideally be universally understood what's happening right now @zacharee . Thank you for providing and maintaining your Apps and your sacrifice of holding onto your verified Account...I do hope to be proven wrong on the above mentioned "concerns". (Probably shouldn't even have mentioned it, not that it would change a thing)

How things are looking so far

DEVELOPER_VERIFICATION_FAILED_REASON_DEVELOPER_BLOCKED

Added in version 36.1 

public static final int DEVELOPER_VERIFICATION_FAILED_REASON_DEVELOPER_BLOCKED 

Developer verification failed because the developer cannot be verified, as reported by the verifier via ERROR(DeveloperVerificationSession.reportVerificationComplete(DeveloperVerificationStatus)/android.content.pm.verify.developer.DeveloperVerificationSession#reportVerificationComplete(android.content.pm.verify.developer.DeveloperVerificationStatus) DeveloperVerificationSession.reportVerificationComplete(DeveloperVerificationStatus)) or ERROR(DeveloperVerificationSession.reportVerificationComplete( DeveloperVerificationStatus, PersistableBundle)/android.content.pm.verify.developer.DeveloperVerificationSession#reportVerificationComplete(android.content.pm.verify.developer.DeveloperVerificationStatus,android.os.PersistableBundle) DeveloperVerificationSession.reportVerificationComplete( DeveloperVerificationStatus, PersistableBundle))

Constant Value: 2 (0x00000002) 

DEVELOPER_VERIFICATION_FAILED_REASON_NETWORK_UNAVAILABLE

Added in version 36.1 

public static final int DEVELOPER_VERIFICATION_FAILED_REASON_NETWORK_UNAVAILABLE 

Developer verification failed because the network is unavailable. This corresponds to the status of ERROR(DeveloperVerificationSession.DEVELOPER_VERIFICATION_INCOMPLETE_NETWORK_UNAVAILABLE/android.content.pm.verify.developer.DeveloperVerificationSession#DEVELOPER_VERIFICATION_INCOMPLETE_NETWORK_UNAVAILABLE DeveloperVerificationSession.DEVELOPER_VERIFICATION_INCOMPLETE_NETWORK_UNAVAILABLE) reported by the verifier via ERROR(DeveloperVerificationSession.reportVerificationIncomplete(int)/android.content.pm.verify.developer.DeveloperVerificationSession#reportVerificationIncomplete(int) DeveloperVerificationSession.reportVerificationIncomplete(int)).

Constant Value: 1 (0x00000001) 

DEVELOPER_VERIFICATION_FAILED_REASON_UNKNOWN

Added in version 36.1 

public static final int DEVELOPER_VERIFICATION_FAILED_REASON_UNKNOWN 

Developer verification failed because of unknown reasons, such as when the verifier times out or cannot be connected. It can also corresponds to the status of ERROR(DeveloperVerificationSession.DEVELOPER_VERIFICATION_INCOMPLETE_UNKNOWN/android.content.pm.verify.developer.DeveloperVerificationSession#DEVELOPER_VERIFICATION_INCOMPLETE_UNKNOWN DeveloperVerificationSession.DEVELOPER_VERIFICATION_INCOMPLETE_UNKNOWN) reported by the verifier via ERROR(DeveloperVerificationSession.reportVerificationIncomplete(int)/android.content.pm.verify.developer.DeveloperVerificationSession#reportVerificationIncomplete(int) DeveloperVerificationSession.reportVerificationIncomplete(int)).

Constant Value: 0 (0x00000000) 

EXTRA_DEVELOPER_VERIFICATION_EXTENSION_RESPONSE

Added in version 36.1 

public static final String EXTRA_DEVELOPER_VERIFICATION_EXTENSION_RESPONSE 

An extra containing the response provided by the developer verifier to any extension params provided by the installer. It will be of type PersistableBundle.

Constant Value: "android.content.pm.extra.DEVELOPER_VERIFICATION_EXTENSION_RESPONSE" 

EXTRA_DEVELOPER_VERIFICATION_FAILURE_REASON

Added in version 36.1 

public static final String EXTRA_DEVELOPER_VERIFICATION_FAILURE_REASON 

When an installation fails because the developer verification was incomplete or blocked, this extra provides a code that explains the reason, such as DEVELOPER_VERIFICATION_FAILED_REASON_NETWORK_UNAVAILABLE. It is included in the installation result returned via the IntentSender in Session.commit(IntentSender). However, along with this reason code, installers can receive different status codes from EXTRA_STATUS depending on their target SDK and permission status: 

Installers without the INSTALL_PACKAGES permission but with the REQUEST_INSTALL_PACKAGES permission and targeting API 36 or less will first receive the STATUS_PENDING_USER_ACTION status code without this reason code. They will be forced through the user action flow to allow the OS to inform the user of such verification context before continuing to fail the install. If the user has the option to bypass the verification result and chooses to do so, the installation will proceed. Otherwise, the installer will receive the STATUS_FAILURE_ABORTED status code along with this reason code that explains why the verification had failed. 

Installers with the INSTALL_PACKAGES permission and targeting API 36 or less will directly receive the STATUS_FAILURE_ABORTED status code. This is because they are not expected to have the capability of handling the STATUS_PENDING_USER_ACTION flow, so the installation will directly fail. This reason code will be supplied to them for providing additional information. 

For all installers targeting higher than API 36: 

For situations that require user input, such as when the developer verification policy allows the user to bypass a verification failure caused by network issues, the installer will receive a STATUS_PENDING_USER_ACTION status code without this reason code. The installer will be forced through the user action flow to allow the OS to inform the user of such verification context before continuing to fail the installation. If the user has the option to bypass the verification result and chooses to do so, the installation will proceed. Otherwise, the install will receive the STATUS_FAILURE_ABORTED status code along with this reason code that explains why the verification had failed. 

For all other situations, the installer will receive a STATUS_FAILURE_ABORTED status code along with this reason code, so the installers can explain the failure to the user accordingly. An Intent.EXTRA_INTENT will also be populated with an intent that can provide additional context where appropriate, should the installer prefer to defer to the OS to explain the failure to the user. 

Constant Value: "android.content.pm.extra.DEVELOPER_VERIFICATION_FAILURE_REASON" 

EXTRA_DEVELOPER_VERIFICATION_LITE_PERFORMED

Added in version 36.1 

public static final String EXTRA_DEVELOPER_VERIFICATION_LITE_PERFORMED 

An extra containing a boolean indicating whether the lite version of the developer verification was performed on the app to be installed. It is included in the installation result returned via the IntentSender in Session.commit(IntentSender) when the installation failed.

Constant Value: "android.content.pm.extra.DEVELOPER_VERIFICATION_LITE_PERFORMED"