## Context Follow-up from review of https://github.com/DFXswiss/bitbox_flutter/pull/28 ## Evidence - PR #28 adds Android and iOS example builds in `.github/workflows/pull-request.yaml` (android job ~line 43, ios job ~line 63). - The same PR also changes macOS paths: - `macos/Classes/BitboxFlutterPlugin.swift` (drops template `getPlatformVersion`) - `example/macos/Runner.xcodeproj/project.pbxproj` and scheme / Podfile / RunnerTests removal - No `flutter build macos` (or equivalent) CI job covers those edits. PR author verified locally; CI does not. ## Suggested fix Optional job on `macos-latest` (can share the iOS runner or be a separate job) with working-directory `example`: flutter build macos --debug using the same Flutter pin as the other jobs. ## Severity Follow-up only — not a merge blocker for #28; improves the native-build gate the PR otherwise introduces.
Context
Follow-up from review of #28
Evidence
.github/workflows/pull-request.yaml(android job ~line 43, ios job ~line 63).macos/Classes/BitboxFlutterPlugin.swift(drops templategetPlatformVersion)example/macos/Runner.xcodeproj/project.pbxprojand scheme / Podfile / RunnerTests removalflutter build macos(or equivalent) CI job covers those edits. PR author verified locally; CI does not.Suggested fix
Optional job on
macos-latest(can share the iOS runner or be a separate job) with working-directoryexample:using the same Flutter pin as the other jobs.
Severity
Follow-up only — not a merge blocker for #28; improves the native-build gate the PR otherwise introduces.