chenxiaolong
Google developer verification
As many folks likely already saw, Google will soon be enforcing developer verification: https://developer.android.com/developer-verification
Once this is in place, Android will refuse to install an app unless the developer has gone through the developer verification process. This applies regardless if the app is installed from Google Play Store, F-Droid, or just opening an .apk file in a file manager. Installing an .apk file without an internet connection will no longer be possible.
The developer verification process requires providing personal information to Google, including the legal address and official government ID. Google can choose to revoke a developer's verification at any time.
I personally view this as an attack on software freedom and will not be participating in this program. I will not provide any personal information to Google nor sign any contract with them just for the privilege of distributing an app outside of Google Play.
This means after Google begins enforcement of this new policy, you will no longer be able to install RSAF or any of my other apps, except via adb install. Google currently exempts adb install from the developer verification restrictions, though there is nothing in the implementation of the verification functionality that guarantees this will always be the case.
Folks with rooted devices or devices running third party OS's will likely not be affected. With root access, it is trivial to disable the developer verification implementation, which exists in a separate proprietary privileged app preinstalled on the device. With third party OS's, the developer verification components likely aren't included in the first place.
Fortunately I have two devices and can use adb over wireless in termux to workaround it if you keep updating.
If you don't plan to keep updating, can I ask to wait until rclone 1.72 comes out at least? That one will have the possibility to mount zip\squash files (locally or remotely I think). Not sure if zstd support for that yet, but other functionality is using zstd so they have the dependency so I feel like it's just a question of time.
Google CEO was at that disgusting meet at the white house earlier this year so I'm not surprised they are trying to squash software freedom. You know, considering they're trying to enslave all of America anyway and turn it into Russia, including human waves tactics and aggressive conquest ideas, preventing people accessing end to end encryption sounds like part of the price.
I plan to keep maintaining RSAF for as long as I use Android and personally have a use for the app (which I currently still do).
Google seems to be easing up on these restrictions now, at least allowing unverified apps through some advanced flow, yet to be described.
Empowering experienced users
While security is crucial, we’ve also heard from developers and power users who have a higher risk tolerance and want the ability to download unverified apps.
Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.
Source: https://android-developers.googleblog.com/2025/11/android-developer-verification-early.html?m=1
