[iamoguzhanarslantas]

Summary

geolocator_watchos 0.1.2: three members that were "Not supported on watchOS", AppleSettings reaching CoreLocation, and two fixes to how streams and single fixes share the location manager.

Not verified on a physical Apple Watch. Everything below was checked on the watchOS 27.0 Simulator and on the host only. I could not get a watch to show up in Xcode, so no device run has been done.

Added

• getLocationAccuracy reports accuracyAuthorization: precise or reduced.
• requestTemporaryFullAccuracy asks with a purpose key and waits for the answer. Without NSLocationTemporaryUsageDescriptionDictionary it throws PermissionDefinitionsNotFoundException, as geolocator does on iOS.
• getServiceStatusStream starts with the current status, then reports each change CoreLocation signals.
• AppleSettings passed to getPositionStream or getCurrentPosition now reach CoreLocation, read through toJson() so the package does not depend on geolocator_apple: activityType (for example ActivityType.fitness for a run) and allowBackgroundLocationUpdates.
• Three FFI exports: geolocator_watchos_accuracy_authorization, _request_temporary_full_accuracy and _accuracy_requests_done. geolocator_watchos_start_updates takes the activity type and the background flag.

Fixed

• getCurrentPosition no longer stops a position stream that is running, and cancelling one of two streams no longer stops the other. They share the one CLLocationManager, which stops when the last of them ends; a call during a stream waits for the stream's next fix without changing its settings.
• A cached fix more than 5 seconds older than the request is no longer returned by getCurrentPosition, nor emitted first by a new stream: CoreLocation hands over its last fix first, however old.

Background flag

allowsBackgroundLocationUpdates turns on only when the Info.plist's UIBackgroundModes has location. CoreLocation asserts and ends the app otherwise, and it reads only UIBackgroundModes on watchOS too: with location under WKBackgroundModes the app ended on the Simulator, and with UIBackgroundModes it runs. So WKBackgroundModes does not count.

Verified

On the watchOS 27.0 Simulator (Apple Watch Series 12, 46 mm):

• The background flag with each Info.plist key, as above.
• getLocationAccuracy and getServiceStatusStream answer.
• The example returns the simulated fix after the permission prompt.
• The example builds with every ffiSymbols entry in the export table.

Off the watch:

• 25 host tests (14 new): accuracy, the service-status stream, the AppleSettings fields, the activity-type mapping, the shared manager with two streams and a single fix during a stream, and the stale cached fix.
• Every tool/ check, dart format as CI runs it, and pub publish --dry-run are clean.

Not verified

• A physical Apple Watch. Nothing has run on a device.
• The temporary full-accuracy prompt: it has not been seen asking.
• Background updates with the wrist down, and what activityType changes in real GPS fixes. The Simulator's fixes are simulated.

Notes for review

• Two commits: the 0.1.2 work, and the review fixes (the UIBackgroundModes-only check, the shared manager, the stale fix).
• The README moves the three members out of "Not supported on watchOS" and adds a section on workouts and background updates.

🤖 Generated with Claude Code

[MAUstaoglu]

Thanks a lot for this, @iamoguzhanarslantas. The new tests are good, and the watchOS availability work is careful. A few things need to change before we can merge.

Must-fix

1. watchos/Classes/geolocator_watchos_ffi.m:150: CLActivityTypeMaritime is declared only in the watchOS 27 SDK, so the plugin no longer compiles with Xcode 26, which flutter-watchos still supports. Please guard it with #if __WATCH_OS_VERSION_MAX_ALLOWED >= 270000. At :152, fall back to CLActivityTypeOtherNavigation, as geolocator_apple does, rather than Other.

2. lib/geolocator_watchos.dart:218-222, 260: one shared location manager serves both single fixes and streams.

   • A getCurrentPosition during a distance-filtered stream times out after 30 s if the wearer stands still.
   • A second stream overwrites the first stream's accuracy and background settings.

   Please mirror geolocator_apple: a separate one-time manager for single fixes, and reuse of the running stream. Add tests for both cases.

3. lib/geolocator_watchos.dart:250: the 5 s staleness filter also applies to streams. Upstream filters only single fixes (GeolocationHandler.m:225), and reduced-accuracy fixes can legitimately be much older.

4. README.md:81 links flutter_watch_workout, which doesn't exist in this repo or on pub.dev.

Nice-to-have

• .m:167: an activity type of 0 keeps the previous value. Please reset it to Other.
• lib:350 calls the blocking +locationServicesEnabled on every fix. Let the callback carry the kind instead (AUTHORING §2b).
• The public GeolocatorWatchosBackend changed shape, so this should be 0.2.0 with a Breaking CHANGELOG entry.
• The activity-type test duplicates the mapping table. Consider testing the real AppleSettings through a geolocator_apple dev_dependency.
• README:
  • mention that allowBackgroundLocationUpdates defaults to true;
  • point to App Review guideline 2.5.4 for background location;
  • say that the temporary full-accuracy prompt and wrist-down updates aren't verified on a device yet.

Note: our CI doesn't compile the .m files yet, so please build the example with both Xcode 26 and 27. We'll start the CI run once you push the update. Thanks again!

Posted from the wrong account; superseded by the maintainer review.

[iamoguzhanarslantas]

Thanks for the review. Pushed 2536ff2, now 0.2.0:

Must-fix

1. CLActivityTypeMaritime is behind #if __WATCH_OS_VERSION_MAX_ALLOWED >= 270000, with CLActivityTypeOtherNavigation as the fallback. I only have Xcode 27.1 here. I compiled the .m against the watchOS 27 SDK with the ceiling forced to 260000 and to 270000, and both compile. A real Xcode 26 build is still needed.
2. getCurrentPosition now has its own CLLocationManager, as in geolocator_apple. It skips fixes older than 5 s and stops after the first one it accepts. getPositionStream returns the running stream with its original settings. Tests cover both cases you listed, plus two concurrent single fixes.
3. The 5 s filter is native and applies to the single-request manager only. Streams emit every delivered fix, counted by a new geolocator_watchos_position_count.
4. The README no longer links flutter_watch_workout.

Nice-to-have

• Activity type 0 resets to CLActivityTypeOther.
• The callback carries a kind (position / authorization / accuracy). The service-status stream calls locationServicesEnabled only on authorization changes, and a test checks that a fix does not call it.
• Version 0.2.0 with a Breaking section.
• geolocator_apple is a dev_dependency, and the tests pass the real AppleSettings.
• README: allowBackgroundLocationUpdates defaults to true, Guideline 2.5.4, and the temporary-accuracy prompt and wrist-down updates are listed as not verified on a device.

Checked: 26 host tests. The example builds for the watchOS 27.0 Simulator with all 13 ffiSymbols exported. On the Simulator, getCurrentPosition returned a simulated location, then the new one after it moved.

🤖 Generated with Claude Code

[MAUstaoglu]

Thanks, @iamoguzhanarslantas. Every point is addressed. We syntax-checked the .m with Xcode 26.6 and 27.0, for device and simulator, and it compiles on both; the previous revision didn't on Xcode 26. Approving.