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.
Description
Fixes #442, XCode Archive : MapLibre.xcframework-ios.signature” couldn’t be copied to “Signatures” because an item with the same name already exists
Library code signing causes issue for both react-native and expo usage. In the past we had a build phase in the expo plugin to remove the *.signature file, but that was wed to xCode 15. Now with 16., the plugin doesn't work. Additionally, for react-native apps the developer must personally remove the *.signature.
It's a pain in the ass. Let's just disable code signing of the library and call it a day.
Checklist
yarn lint:fix
in the root folderyarn test
in the root folderyarn generate
in the root folderCHANGELOG.md
index.d.ts
)/example
)