fix: plugin remove obsolete gradle.properties
#621
Merged
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.
Previously the Expo plugin would have not remove a property, when removing it from
app.json
orapp.config.{js,ts}
. It only overwrote duplicates. This should not be the case, as it would leave artifacts within the generatedgradle.properties
, making the plugins output for Android non-deterministic. For example the broken behavior previously:locationEngine: "google"
inapp.config.ts
expo prebuild
This will add
org.maplibre.reactnative.locationEngine=google
togradle.properties
locationEngine: "google"
inapp.config.ts
againexpo prebuild
org.maplibre.reactnative.locationEngine=google
will still be ingradle.properties
Now all old properties from MLRN are removed and only the current plugin props are applied.