NativeScript / NativeScript/plugins
[@nativescript/geolocation] iOS - This method can cause UI unresponsiveness if invoked on the main thread. Instead, consider waiting for the `-locationManagerDidChangeAuthorization:` callback and checking `authorizationStatus` first.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 206
- Forks
- 123
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 1
Description
CoreLocation - This method can cause UI unresponsiveness if invoked on the main thread. Instead, consider waiting for the -locationManagerDidChangeAuthorization: callback and checking authorizationStatus first.
Has Apple changed something that means it doesn't like this Library anymore?
In my application my Info.plist looks like this
<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>Tracks your location and delivery accuracy</string>
<key>UIBackgroundModes</key>
<array>
<string>location</string>
</array>
I am using @nativescript/geolocation 9.0.0
Is there a plan to move this off the main thread? or can I do something to ensure it doesn't execute on the main thread?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the iOS implementation for @nativescript/geolocation and the CoreLocation authorization call mentioned in the warning. Compare its behavior with the locationManagerDidChangeAuthorization callback and authorizationStatus check; done means the warning is addressed without breaking location permission handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100