feat(iOS): Add Fake GPS iOS support#452
Open
gustavoabel wants to merge 1 commit intoAgontuk:masterfrom
Open
Conversation
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
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
This pull request adds fake GPS (mock location) detection support by exposing whether a location was simulated by software.
A new mocked field is added to the location object, using the native
sourceInformation.isSimulatedBySoftwareflag when available, with a safe fallback to false for compatibility with older iOS versions.This allows applications using
react-native-geolocation-serviceto reliably detect mocked locations and apply additional validation or security rules when needed.Test Plan
Tested on iOS device/emulator with:
Mock location app enabled → mocked returns true
Real GPS location → mocked returns false
Verified backward compatibility on devices where sourceInformation is not available
Confirmed no breaking changes to the existing location API
Ensured the new field is optional and safely defaults to false