Google: 'Your $1000 phone needs our permission to install apps now'". Android users are screwed - Louis Rossmann
Google: 'Your $1000 phone needs our permission to install apps now'". Android users are screwed - Louis Rossmann
You're viewing a single thread.
516 comments
-
How does this affect "second-party" apps (i.e. apps you have created yourself)? Are you still allowed to go to Android studio, make an APK, transfer it to your own phone, and install that app? If no, this spells the death of experimental indie developers on Android.
-
yes. from what I understand, you will get a developer key from Google, and then you will sign your APK with your key.
you'll still be able to sideload apps that have been signed with developer keys. the main point here is that Google is forcing the developer to identify themselves.
-
You don't need to sign anything just turn off play protect with 1 adb command:
undefined
adb shell settings get global package_verifier_user_consent adb shell settings put global package_verifier_user_consent -1 # disable Play Protect
-
Not a solution to our problem, but this is a crumb in our favor.
-
I know why you included both, but saying "1 adb command" and then posting two is funny to me.
-
One gets the current value to verify it and another actually sets a new value. It's the way these commands are usually shared.
-
-
Does this work with any app or just second party ones? Can you re-enable it?
-
Yes it modifies the phone not the app and you can re-enable it anytime with 1 instead of -1
-
-
-
-
They might copy from apple. 3 apps with a self signed cert that needs to be renewed every week...
-
516 comments