New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submit existing iTC builds to Review instead of uploading a new one #64
Comments
I agree, it would make sense to submit the same build for review, which you already had in TestFlight. How would we approach this? Right now, Not sure, if there is a big advantage is submitting the same build? |
So i think the Then when you do a |
I'm not sure I completely agree. This would also mean, you have to use Apple TestFlight, which many people don't. |
Fair point. But I think this workflow situation should be supported. And for those that don't use test flight it should do the same like ur suggesting by using the same build somehow |
I'll close this issue for now, thanks for your feedback 👍 |
So when looking at the Fastane configuration, i am not sure if it makes sense with the new Apple TestFlight. The new Apple Testflight lets you take a beta build and then make it the live build.
I propose the beta flow uploads the correct metadata for what the new version will be, with the snapshots and all. And then the App Store flow would basically just auto mark the beta upload to be the live version.
Thoughts, ideas?
The text was updated successfully, but these errors were encountered: