fix(android): use double type for GPSHPositioningError tag#30
Merged
Conversation
Android ExifInterface expects IFD_FORMAT_URATIONAL for this tag. Using string type caused setAttribute to silently fail on write.
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.
Summary
Android's
ExifInterfaceexpectsIFD_FORMAT_URATIONALforGPSHPositioningError. The tag was typed as"string"inExifyTags.kt, causingsetAttributeto silently fail on write. Changed to"double"so the value goes throughdecimalToRational()— matching the expected rational format.Type of Change
Test Plan
Verified on both iOS and Android that
GPSHPositioningErrorpersists after write and reads back correctly.Checklist