Updating Your Published App

After your app is live, you’ll need to push updates — bug fixes, new features, or store listing improvements. The process is simpler than the first submission, but there are a few things to know.

When to update

• Bug fixes — Fix issues reported by users or discovered in reviews
• New features — Expand your app based on user feedback
• Store listing improvements — Update screenshots, descriptions, or keywords based on performance data
• OS compatibility — Both stores periodically require apps to target newer OS versions
• Regular cadence — Both stores favor apps that update regularly. Monthly updates are a good target.

Tip

Regular updates signal to the stores that your app is actively maintained. This improves search rankings and makes your app eligible for editorial features. Even small improvements count.

Update workflow

Google Play

1. Make changes in Primio

   Describe the updates you want — bug fixes, new features, design changes.

2. Build a new AAB

   Go to Workspace → Publish → Android → Build AAB. Primio increments the build number automatically.

3. Test on a real device

   Build an APK first (cheaper) and test the changes on your phone before uploading the AAB.

4. Upload to Google Play Console

   Go to your app → Release → Production → Create new release. Upload the new AAB.

5. Write release notes

   Describe what changed in this version. Users see this on your listing under “What’s new.” Keep it brief and user-friendly:

   • “Fixed a crash when saving profile photos”
   • “Added dark mode”
   • “Improved loading speed on the home screen”

6. Choose rollout percentage (optional)

   Google lets you do staged rollouts — release to 10% of users first, then increase to 50%, then 100%. This is optional but useful for catching issues before they affect everyone.

7. Submit for review

   Updates go through review just like the initial submission, but reviews are typically faster — usually hours to a couple of days.

App Store

1. Make changes in Primio

   Describe the updates you want — bug fixes, new features, design changes.

2. Build a new IPA

   Go to Workspace → Publish → iOS. Upload your .p8 credentials and build.

3. Test with TestFlight

   Upload the new IPA via Transporter. Test on a real device via TestFlight before submitting for review.

4. Create a new version in App Store Connect

   Go to your app → click + Version or Platform → add a new version number (e.g., 1.1.0).

5. Select the new build

   Choose the build you just uploaded via Transporter.

6. Write “What’s New” text

   This appears on your listing. Describe changes in plain language for users.

7. Update store listing (optional)

   You can update screenshots, description, or keywords alongside the new version. This is a good opportunity to refresh your listing.

8. Submit for review

   Apple reviews updates in 24-48 hours, sometimes faster. Updates are reviewed for the same guidelines as the initial submission.

Version numbers

Primio increments the build number automatically with each build. The version number (e.g., “1.2.0”) is managed by you — update it when you want to signal a new release to users.

If you see “version already exists” or “build already exists”:

• Rebuild in Primio — each build generates a new, higher build number
• On Google Play, every new AAB must have a higher versionCode than the one currently live
• On the App Store, every new IPA must have a higher build number than any previously uploaded build (even rejected ones)

Note

The version number users see (e.g., “1.2.0”) and the build number (an internal integer) are different. Primio auto-increments the build number with each build. The user-visible version follows semantic versioning (major.minor.patch) and is up to you to update when needed.

Updating your store listing without a new build

You can update certain parts of your store listing without uploading a new build:

Google Play

These can be changed anytime without a new release:

• Store listing text (name, description, short description)
• Screenshots and feature graphic
• Contact information
• Privacy policy URL

Changes go through a brief review (usually hours).

App Store

These require a new version submission:

• Screenshots
• Description
• Keywords
• What’s New text

You must attach a new build to submit updated metadata. However, you can use the same build if only the metadata changed — just create a new version, select the existing build, and submit.

How often to update

Frequency	Good for	What to change
Weekly	Apps with active users reporting bugs	Critical bug fixes only
Monthly	Most apps (recommended cadence)	Bug fixes + small improvements
Quarterly	Stable apps with few issues	Feature additions, store listing refresh

Both stores check when your app was last updated. Apps that haven’t been updated in over a year may receive warnings or reduced visibility. On Google Play, apps must target a recent Android API level — if yours falls behind, Google notifies you with a deadline to update.

Next steps

App Store Optimization

Optimize your listing each time you update — refresh keywords, screenshots, and descriptions.

Handling Rejections

What to do if an update gets rejected — same process as initial rejections.