Play Store & App Store publishing
Release a New Version of Your App on Google Play
Version bump, signing and a clean Play release — without breaking your keystore.
Delivered in 1 working day
Fixed price · per issue · no hidden charges
or
Ask on WhatsApp before you buyA real person replies — usually within minutes during the day (IST).
How it works
- Pay ₹999Secure checkout with your package name.
- We build and signYou share the code or AAB on WhatsApp; we prepare a signed release.
- ReleasedSubmitted to Google Play within 1 working day.
The short answer
ZoopCoder releases a new version of an existing Android app on Google Play for ₹999 per release, submitted within one working day. Every update must carry a higher versionCode than the live one and be signed with the same upload key, otherwise Play Console rejects the upload. We can use a staged rollout so the new version reaches a small percentage of users first.
What you get
- versionCode and versionName increased
- Signed release AAB built with your upload key
- Release notes written
- Production or testing track release created
- Optional staged rollout percentage
- Submitted for review and monitored
| Price | ₹999/issue (fixed) |
|---|---|
| Deliverable | New version submitted on Play |
| Timeline | 1 working day |
| Tracks | Production, open, closed or internal testing |
| Rollout | Full or staged |
| Price basis | Per release |
What we need from you
- Updated source code or AAB
- Upload keystore, or Play Console access if Play App Signing is on
- What changed in this version
Not included
- Writing the new features or fixes themselves
- Google's review time
About this service
Releases break in boring ways: a versionCode that was not increased, an AAB signed with the wrong key, or a lost keystore. We handle the mechanics carefully and never change your signing key without telling you. If your app uses Play App Signing, a lost upload key can be reset through Google — we can help file that request. Staged rollout is useful for bigger changes: release to 10% of users, watch crash reports, then go to 100%. One thing that surprises people managing their own Play Console: nothing is submitted automatically. Google's own documentation puts every unsent edit — a version bump, new release notes, even a store-listing change — under a distinct 'Changes not yet sent for review' status until you explicitly send it; close the tab after editing and it sits there in draft indefinitely, not live and not in review.
Questions before you buy
I lost my keystore. Can I still update?
If Play App Signing is on, yes — you can request an upload key reset from Google. If not, the app cannot be updated under the same listing.
What is a staged rollout?
Releasing an update to a percentage of users first, so problems affect fewer people.
Can you make the code changes too?
Yes, small fixes are available as a website/app bug fix at ₹999 per issue.
How long does review take for updates?
Often hours to a couple of days, decided by Google.
I edited something in Play Console but it never went live. Why?
Play Console never submits automatically. Every change — a version bump, release notes, even a store-listing edit — sits under a "Changes not yet sent for review" status until you explicitly send it, per Google's own Play Console documentation. Closing the tab after editing leaves it in draft indefinitely.
So how long does Google actually take once it is sent?
Standard publishing processes updates "as soon as possible", but Google states that certain apps get extended reviews that "may result in review times of up to seven days or longer in exceptional cases" — there is no fixed SLA either way.
Often ordered with this
© 2026 ZoopCoder