![]() Update the ist: You will also need to update the CFBundleVersion key in your ist file to match the incremented build number. The build number is separate from the version number and doesn't require App Store review. You can find this in your project settings under the "General" tab. Increment the Build Number: In your Xcode project, go to the target settings and increment the build number for each new build you want to upload. However, you can work around this by using build numbers instead of version numbers for your TestFlight builds. Apple enforces strict versioning rules to ensure consistency and prevent confusion for users. ![]() Is it possible to add new builds without increasing the version? I understand that increasing version number will solve this problem but I don't want to do it for every new build since I will use it just for TestFlight, and increasing version number requires a review time. The train version '1.0.2' is closed for new build submissions.Ĭurrent version published in App Store is 1.0.2, and I want to upload a build 1.0.2+2 just to use for testing in TestFlight. ![]() Please find more information about CFBundleShortVersionString at The value for key CFBundleShortVersionString in the ist file must contain a higher version than that of the previously approved version. I am trying to upload a new build to the App Store Connect for testing in TestFlight for our app which is published in App Store, but Transporter gives this errors: Asset validation failed (90062)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |