Open
Conversation
…t to output files Xcode 15 no longer always writes Info.plist before shell scripts run, so it's safer to write a completely separate Info.plist to another location and then have Xcode use the generated Info.plist
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
1 participant
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.
Trying to update the generated Info.plist directly in the built product no longer works reliably with Xcode 15. Instead we now read the input Info.plist, write an updated Info.plist to a temporary location, then use the generated Info.plist as the Info.plist file in the target settings.
Note that this approach won't work if
GENERATE_INFOPLIST_FILEisYES(which we don't use in our projects).Also updates to Swift 5, builds a universal binary, and other cleanup.