Publish official build under existing Play listing (com.olipsia.jopiter)#16
Merged
Conversation
…ia.jopiter) The Play Store listing for Jopiter was created by the legacy app and keeps its original, immutable package name com.olipsia.jopiter — probing the Play API with the service account showed app.jopiter is 404 while com.olipsia.jopiter resolves. Override the applicationId of the official (store) flavor and the fastlane package_name so releases update the existing app. Code namespace and other variants stay app.jopiter. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X5cqJDzZvxqTxMTWcN2jvm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Play Store listing for Jopiter was created by the legacy app and keeps its original, immutable package name
com.olipsia.jopiter. Probing the Play Developer API with the release service account confirmed it:app.jopiter→ 404 Package not found, whilecom.olipsia.jopiter→ OK.So the release that failed to upload wasn't a permission problem — the app simply doesn't exist under
app.jopiter. This overrides theapplicationIdof the official (store) flavor and the fastlanepackage_nametocom.olipsia.jopiter, so releases update the existing listing (with its current users/reviews). The code namespace and theunofficial/debug variants stayapp.jopiter.Verified locally:
assembleOfficialReleasebuilds and the APK'sapplicationIdiscom.olipsia.jopiter.Merging triggers a Release run that should now upload successfully to production.
🤖 Generated with Claude Code