games_services_watchos #

The watchOS implementation of games_services.

games_services covers iOS, macOS and Android. This package supplies the wrist, which it does not: watchOS has no method channels, so the upstream MethodChannelGamesServices default cannot work there, and this registers itself in its place and talks to GameKit through exported C symbols over dart:ffi.

Usage #

games_services does not include a watchOS implementation, so add this package alongside it; the implementation registers itself.

dependencies:
  games_services: ^4.1.1
  games_services_watchos: ^0.1.0

This release implements games_services_platform_interface 4.x, so it works with games_services 4.x. games_services 5.x requires the 5.x interface, which this package does not implement yet, so games_services: ^5 does not resolve alongside it.

Then use games_services as normal:

await GameAuth.signIn();
await GamesServices.submitScore(
  score: Score(iOSLeaderboardID: 'your.leaderboard.id', value: 42),
);
final rows = await Leaderboards.loadLeaderboardScores(
  iOSLeaderboardID: 'your.leaderboard.id',
  scope: PlayerScope.global,
  timeScope: TimeScope.allTime,
  maxResults: 10,
);

What is supported #

The other members keep the platform interface's UnimplementedError default rather than returning a plausible-looking empty value; see "Not supported on watchOS" below.

Because there is no system leaderboard UI on watchOS, a watch app draws its own from loadLeaderboardScores.

watchOS specifics worth knowing #

• No stable player identifier. gamePlayerID, teamPlayerID and guestIdentifier are all unavailable on watchOS, so the local player's own row is identified by matching rank against the localPlayerEntry GameKit returns alongside the list. scoreHolder.playerID is therefore always null — the upstream model already allows this, since Android omits it for privacy.
• A different authenticateHandler. On watchOS the block takes only an error; the iOS signature with a UIViewController does not exist.
• Failure and emptiness are distinct. loadLeaderboardScores returns null when the read failed and an empty list when the leaderboard has no entries. Collapsing the two makes a broken leaderboard look like an empty one, which is a genuinely hard bug to see.

Not supported on watchOS #

These members of games_services_platform_interface 4.1.1 throw or fail on watchOS. PORTING_REPORT.md lists every member under "Interface coverage".

Status #

Sign-in and score submission have been observed working on a physical Apple Watch; leaderboard reads have not yet. See PORTING_REPORT.md for the verification table.