-
Notifications
You must be signed in to change notification settings - Fork 1
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
Event's date layout #67
Comments
@pkritzinger Can we close this issue? |
Yes you need to use always the last version. At the moment the marketing version 1.0 isn't updated each time. Only the build number (the number between parenthesis) changes on each TestFlight release. |
@matax87 Paul is only inside the external testers, so the problem there is as follows: ...whereas, in the internal testers section, all those versions are marked as "Testing". What do I need to change, that it works also for external testers? In the meantime, I invite @pkritzinger to the internal tester group |
@matax87 Found it... please forget about the question... simple... |
@pkritzinger Now the new version should be send out to you soon, sorry about this... thought the step is automated already |
Internal testers receive each new build immediately after Apple server process the build. Builds must instead be released manually to external testers. Side note: builds with the same version number (but different build number) will be released as soon as they’re added to the specific group without requiring Apples’s review. The operation I don’t think can be automated (at least without making each pipeline taking much longer polling for changes) with the CD as the build once submitted needs to be processed before it can be assigned to a group. |
The newest version should be 1.0 (20211018071950) ... where the build number is composed of "year-month-day-hour-minute-seconds-..." |
The text was updated successfully, but these errors were encountered: