Skip to content

RCTLocationObserver accuracy reset bug? #17145

Closed
@sakarit-zz

Description

@sakarit-zz

_locationManager.desiredAccuracy = RCT_DEFAULT_LOCATION_ACCURACY;

Is there a bug here? I don't understand why the desiredAccuracy should be reset to DEFAULT if enableHighAccuracy is enabled and the desiredAccuracy is initially kCLLocationAccuracyBest.

Also I think this should be added to beginLocationUpdatesWithDesiredAccuracy

_locationManager.pausesLocationUpdatesAutomatically = NO;

so location updates would not pause when using watchPosition

Metadata

Metadata

Assignees

No one assigned

    Labels

    Ran CommandsOne of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions