Fix logic error for TestFlight expiration#2097
Merged
Merged
Conversation
Contributor
Author
|
This has been tested successfully using Browser Build. |
Joerg-Schoemer
pushed a commit
to Joerg-Schoemer/Loop
that referenced
this pull request
Jan 11, 2024
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
2 participants
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.
Now that some users of Browser Build method have profile expirations that are shorter than 90 days after the build, we see that the TestFlight expiration continues to be 90 days after build date.
In other words, TestFlight expiration is independent of profile expiration.
Remove the logic that considers profile expiration for a TestFlight build.
This has been tested with a Mac-Xcode build.