LATEST: AppYet v4.2.7 Released
- Thread starter appyet
- Start date
easieritplaystore
New Member
Treece
New Member
It was posted in another thread, but figured it needed to be here, too. You can extend your deadline with Play Store for the SDK and 16k policies. I did it today and was extended to Oct 31, 2025, then I updated my app. Go to your app, then Monitor & Improve > Policy & Programs > Policy Status and click on each one, scroll to the bottom, apply for the extension. Mine were granted immediately (selected two options for why, external audits required and awaiting new SDK from provider). Good luck.
@appyet - FIX THIS SHIT ALREADY. The money you make from all of our apps is insane for not having near-immediate response times from you on critical issues.
@appyet - FIX THIS SHIT ALREADY. The money you make from all of our apps is insane for not having near-immediate response times from you on critical issues.
mariotecno
Member
Hello AppYet team, @appyet
I have repeatedly emailed regarding the required updates for compliance with Google Play policies, including the new SDK and other mandatory changes. Despite multiple attempts, there has been no response, and the platform remains outdated.
As this affects all my apps and puts them at serious risk of suspension or removal from the Play Store, I have reported this issue directly to the Google Play Console.
Immediate action from AppYet is required to resolve this critical issue. Delays are unacceptable and jeopardize the status of developers relying on your platform.
I have repeatedly emailed regarding the required updates for compliance with Google Play policies, including the new SDK and other mandatory changes. Despite multiple attempts, there has been no response, and the platform remains outdated.
As this affects all my apps and puts them at serious risk of suspension or removal from the Play Store, I have reported this issue directly to the Google Play Console.
Immediate action from AppYet is required to resolve this critical issue. Delays are unacceptable and jeopardize the status of developers relying on your platform.
That’s a smart move — learning Flutter will give you way more control over your projects and help you avoid being dependent on limited platforms. It’s a great framework, especially if you want to build something flexible and cross-platform.
By the way, if you ever need professional help or want to see how it’s done at a higher level, take a look at https://www.cogniteq.com/flutter-app-development — they’ve got some really solid examples of what can be achieved with Flutter.
monkeycoderswm
New Member
You can easily update to your private key created in Android Studio, but after requesting you must wait 48-72h and after that you can update app with Android Studio .aab
monkeycoderswm
New Member
Android Studio: Generate Signed Android App Bundle > Save Key with name your_alias.jks (for example YourApp.jks) to any location on your PC > and open CMD and type this:
Code:
"C:\Program Files\Android\Android Studio\jbr\bin\keytool.exe" -exportcert -rfc ^
-alias [your alias] ^
-file "[your location of key]\upload_cert.pem" ^
-keystore "[your location of key]\[your alias].jks"
"C:\Program Files\Android\Android Studio\jbr\bin\keytool.exe" -list -v ^
-keystore "[your location of key]\[your alias].jks" -alias [your alias](change text in brackets to your location and/or alias)
And upload .pem file to Google Play, above is instruction how to do this in Google Play.
helloworld
New Member
That's great to know, thanks!
Have you ever managed to update an app this way?
monkeycoderswm
New Member
Yes, my 4 apps updated this way
mariotecno
Member
What tools did you use to open the source code of the apk file in Android Studio?
easieritplaystore
New Member
let say it:
TL;DR:
You can update even if you lost your local keystore:
If your builder lets you export the per-app keystore, that’s the clean fix for legacy (non-enrolled) apps. Export it, keep it safe, and consider enrolling the app into Play App Signing right after.
Summary if @appyet do update is fine all good, if not and they decide to provide keystore is fine to. If both not and we not signed to app signing then all apps this way is to deprecate
Lost keystore? Can I still update my Android app?
TL;DR:
- If your app is NOT enrolled in Google Play App Signing and you don’t have the original keystore, you cannot publish updates to that package. Your choices are: recover the keystore (e.g., from your builder) or ship a new app with a new package name and migrate users.
- If your app IS enrolled in Play App Signing, you can keep updating by resetting the upload key (no need for the old keystore). Sign your next AAB with the new upload key; Play will re-sign delivery with the app-signing key it already holds.
Why this happens (two keys, two roles)
- Upload key: what you use to sign uploads (AAB) to Play Console. This can be reset.
- App-signing key: what Google Play uses to sign the APKs that users actually install. If your app is enrolled, Google stores this; you never need to download it.
Case A — Not enrolled in Play App Signing
- Without the original keystore/private key, you cannot produce a valid update for that package.
- Options:
- Recover the keystore (e.g., if your app builder lets you export the per-app keystore from your account panel). || Heres we need reaction from @appyet
- If you can’t recover it, deprecate that package and publish a new app (new package name).
- If you do recover the key, update as normal; also consider enrolling in Play App Signing immediately so this can’t bite you again.
Case B — Enrolled in Play App Signing (not my case)
You can update even if you lost your local keystore:
- Generate a fresh upload keystore:
keytool -genkeypair -v -keystore upload-keystore.jks -alias upload \
-keyalg RSA -keysize 2048 -validity 10000 \
-storepass <STORE_PASS> -keypass <KEY_PASS> \
-dname "CN=Your Name, O=YourOrg, C=US"
keytool -export -rfc -keystore upload-keystore.jks -alias upload -file upload_certificate.pem - In Play Console → App integrity → Upload key certificate → Request upload key reset and upload upload_certificate.pem.
- Build your AAB, sign it with the new upload keystore, and upload. Play will re-sign with your app-signing key for users.
App builders (in this case AppYet)
If your builder lets you export the per-app keystore, that’s the clean fix for legacy (non-enrolled) apps. Export it, keep it safe, and consider enrolling the app into Play App Signing right after.
If you must deprecate (no key + not enrolled)
- Publish a new package and communicate the move:
- Add an in-app banner in the old app (if you still control it).
- Use deep links or an “Import account” flow to ease migration.
- Update store listing text to point users to the new app.
Good hygiene going forward
- Store keystores + passwords in a secure password manager, keep an offline backup, and restrict access.
- Prefer Play App Signing so a lost upload key is recoverable (you just reset it).
- Avoid reusing one key across many apps unless you truly need signature-based sharing.
Summary if @appyet do update is fine all good, if not and they decide to provide keystore is fine to. If both not and we not signed to app signing then all apps this way is to deprecate
dariocoutinho
New Member
Is it possible to update the app to another service apk like AppMySite?
easieritplaystore
New Member
only if was Enrolled in Play App Signing then u can reset and upload from new service (keystore), if wasnt pray
or make new package and bring people back to it, anyhow good luck.Harish Bhatti
Member
mariotecno
Member
Muhibullah
New Member
You can ask for another extension until 31 May 2026
easieritplaystore
New Member
this will not work due to target of build
dariocoutinho
New Member
My app need Targeting Android 15 (API level 35) how i do that?
easieritplaystore
New Member
only @appyet can update your apps so u can publish. So till they update it only one option is consider all apps as depreciated cause you need unpublish and rename them adding (depreciated) to name in store or google will remove them tomorrow or later today but if google do remove them but you risk your account banned (then no restore). sad but true. Its GoogleToS.
Last edited: