react-native-nitro-geolocation

unchanged 2.0.4 package JavaScript runs over the installed provider, whose Swift (NitroGeolocation, NitroGeolocationCompat) is compiled to wasm by the Nitro source path on Linux with no Mac or pod executable; no seam or stub answers it. Observed through Peach's simulated permission and location: checkPermission, accuracyAuthorization, getProviderStatus and watchPosition follow the simulated state, a denied grant rejects getCurrentPosition and the watch error callback with permissionDenied, and getLastKnownPosition returns the set coordinate. The score stays 0 until behavior is compared with a version-matched native oracle.
0%
API coverage
No visual proof cases have been published for this package yet. The registry summary below describes what the compat layer implements.
Working (5)
provider compilesregisters and runs; permission undeterminedgranted and denied stateswatch updateslast-known position and the permissionDenied error path observed
Missing
location behavior is not compared with a native oracle; altitude, speed and heading set through the simulated location did not reach getLastKnownPosition (null), reduced accuracy authorization was not observed to change, and a one-shot getCurrentPosition issued while a watch is already updating timed out