Getting "version number has been previously used" but uploading via Transporter succeeds #21372
Unanswered
skytreader
asked this question in
Q&A
Replies: 3 comments 2 replies
-
@skytreader Hi Chad, did you ever resolve this? I'm getting the same error with CircleCI/fastlane and to our knowledge we didn't change anything on our end. Thanks, Neil |
Beta Was this translation helpful? Give feedback.
0 replies
-
Seeing this as well |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey @ronyfadel, @nwainwright, @skytreader. I'm facing this as well, curious if there's any fix/workaround here. Appreciate any help, many thanks! |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a fastlane installation in a CI worker machine. All releases are automated through this and it uploads to other app stores in addition to Apple's.
However, lately we are getting the following error, seemingly out of the blue:
What's confusing is that uploads to other app stores (bearing the same version) succeeds. Also, uploading via Transporter with the same version number also succeeds.
What else can I check here? How exactly does fastlane perform this check? I suspect fastlane has some kind of internal tracking that fails to correspond to the actual state in the app store. Is there any way to reset this?
Beta Was this translation helpful? Give feedback.
All reactions