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.
Closes #3479
What has been done to verify that this works as intended?
I reproduced the crash and confirmed the pr fixes the issue. I also debugged the code to confirm that the code I removes was redundant.
Why is this the best possible solution? Were any other approaches considered?
Just to clarify: the issue is not related to changing the layer to
None
but generally to changing any layers.The crash was caused here because we tried to remove a layer that doesn't exist. It didn't cause a problem when we had mapbxox v8.3.0 but since we updated to 8.4.0 it's been crashing.
I removed the code because as I said above it always tried to remove a layer that didn't exist. The code was redundant. It was called just in
loadReferenceOverlay()
which is called in two places:https://github.com/opendatakit/collect/blob/master/collect_app/src/main/java/org/odk/collect/android/geo/MapboxMapFragment.java#L208
https://github.com/opendatakit/collect/blob/master/collect_app/src/main/java/org/odk/collect/android/geo/MapboxMapFragment.java#L161
in both cases after we call:
map.setStyle
what clears layers we then again tried to remove.How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Testing changing layers in Mapbox would be enough. Nothing else should be affected.
Do we need any specific form for testing your changes? If so, please attach one.
Any form with geo widgets.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:
./gradlew checkAll
and confirmed all checks still pass OR confirm CircleCI build passes and run./gradlew connectedDebugAndroidTest
locally.