Troubleshoot releases and prompts

Start with the app and platform affected. Publishing iOS does not publish Android, and the public changelog's visibility is separate from the in-app update check.

The app does not show an updateCopy Anchor Link

1. Open the app's Releases tab. Confirm that the intended platform has an Unpublish ios or Unpublish android button. A Publish button means that target is still a draft.
2. Compare its Build number with the installed native build, not the visible version. A device at or above the highest published build has no pending update.
3. Check the target's Update mode. An Optional prompt that already appeared on this device does not repeat for the same target build.
4. Confirm with the person maintaining the integration that it uses this app's public App ID and matching native identifier. The dashboard's Integration step does not verify connectivity.
5. Check that the device has a working network connection. A failed check does not force a new update prompt.

Returning to the foreground is not an immediate refresh after every dashboard change. By default, a foreground check is eligible only after six hours since the last successful check. A fresh app launch performs an initial check. See when checks happen.

If the integration reports invalid metadata, verify its native identifier, version, numeric build, and locale. Expo Go's host metadata is not your store app's metadata. See SDK installation.

Do not clear users' app storage as a routine fix. It removes local seen history and may remove other app data too.

Optional notes do not appear again after installationCopy Anchor Link

This can be expected. Notes already shown before an update are not repeated afterward. A What's new screen appears only for unseen notes of an installed published build when there is no pending update.

Editing the notes, changing their language, or republishing the same target does not create a new build or reset local seen state.

An Optional release produces a Required promptCopy Anchor Link

Review all published targets for that platform. An earlier Required build can still set the minimum supported build. A device below that minimum receives Required behavior for the latest target even if that target is Optional.

Use the Required mode explanation to review the policy before changing or unpublishing targets. Unpublishing does not close an already visible Required prompt automatically.

The update button does not open the storeCopy Anchor Link

Open the app's Settings and check App Store URL or Google Play URL. Verify the link yourself and confirm that the intended build is downloadable for the affected users. VibeUpdate does not verify store availability or install the app.

If the URL is correct, ask the person maintaining the mobile integration to inspect its store-opening error or custom store callback. A failed store action leaves a Required prompt visible.

Release notes use an unexpected languageCopy Anchor Link

Check that the release has the requested locale or its base language, and that the selected entry contains shared notes or the relevant platform override. An empty exact-locale entry can fall back to the app default instead of the base language.

On the public page, All uses shared notes. Select iOS or Android to see a platform override. SDK button labels have their own language fallback. See Translate release notes and Component props.

The public page is missing or emptyCopy Anchor Link

• If the URL returns a not-found page, check Public changelog > Public page enabled and save the setting. Check that the app has not been deleted.
• If it shows No releases yet, check that the selected platform has published targets. Drafts do not appear there.
• If a newly published release is not first in the list, compare publication dates. Republishing preserves the target's original publication date.
• If the page opens through its link but does not appear in a search engine, review Allow search indexing. Enabling indexing does not guarantee a search listing.

Preview public page opens the live public page, not a draft preview. See Share your public changelog.

A save, publish, or access request failsCopy Anchor Link

Keep the error message and check the relevant guide:

• App settings and field requirements.
• Publishing prerequisites.
• Version and build-number conflicts.
• Account and payment confirmation.
• Expired or revoked agent tokens.

If a response was interrupted, reopen the affected app or release and check its saved state before repeating the action. Do not repeat a payment or a destructive action merely because its confirmation was not visible.