feat(android): Fallback option for no network or Play Services#53
Merged
OS-pedrogustavobilro merged 4 commits intonextfrom Oct 6, 2025
Merged
feat(android): Fallback option for no network or Play Services#53OS-pedrogustavobilro merged 4 commits intonextfrom
OS-pedrogustavobilro merged 4 commits intonextfrom
Conversation
OS-ruimoreiramendes
approved these changes
Oct 6, 2025
capacitor-bot
pushed a commit
that referenced
this pull request
Oct 6, 2025
# [8.0.0-next.3](v8.0.0-next.2...v8.0.0-next.3) (2025-10-06) ### Features * **android:** Fallback option for no network or Play Services ([#53](#53)) ([09277b7](09277b7))
capacitor-bot
pushed a commit
that referenced
this pull request
Dec 8, 2025
# [8.0.0](v7.1.6...v8.0.0) (2025-12-08) ### Bug Fixes * **android:** use 'propName = value' assignment syntax in build.gradle files ([08f311a](08f311a)) * **ios:** added timeout implementation for both getCurrentPosition and watchPosition ([#55](#55)) ([4c22ac3](4c22ac3)) * peerDependency for pnpm compatibility ([a94839d](a94839d)) ### Features * **android:** Fallback option for no network or Play Services ([#53](#53)) ([09277b7](09277b7)) * **android:** New parameter `interval` in `watchPosition` ([#62](#62)) ([7fda0cf](7fda0cf)) * Capacitor 8 support ([6ead26a](6ead26a)) ### BREAKING CHANGES * **android:** The `timeout` property now gets applied to all requests on Android on iOS, as opposed to just web and `getCurrentPosition` on Android. This aligns with what is documented in the plugin. If you are experiencing timeouts when requesting location in your app, consider using a higher `timeout` value. For `watchPosition` on Android, you may use the `interval` parameter introduced in version 8.0.0. * Capacitor major version update requires major version update on the plugin.
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
2 participants
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.
Description
Provide a new option to use Android Framework's LocationManager when using Play Services pre-conditions check fail - e.g. devices without Play Services or no network.
Context
This PR addresses #45, #39 and #31
Other related links:
Type of changes
Platforms affected
Tests
Feel free to test with the example app in the repository - You should be able to get location without network, or at the very least, not receive
OS-PLUG-0016error anymore.Checklist
RNMT-XXXX <title>