Re-check bonsoir 7.x on Android and iOS against a newer SDK; relax the 6.0.2 pin if it builds
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 54/100
Research direction
Start with native-test-apps/flutter/pubspec.yaml, the Android configuration under native-test-apps/flutter/android, and the advertiser at lib/probe_advertiser.dart. Record the available Android SDK platform, Android Gradle Plugin and Kotlin versions, then try the specified Android and iOS profile builds and run flutter analyze lib/probe_advertiser.dart. If builds and analysis pass, verify Bonjour discovery on a physical WiFi device and update the fixture and docs; otherwise report the exact failure details and keep the 6.0.2 pin.
Written by the indexing model from the issue text.
Description
Follow-up to #379.
Why
The ProbeAdvertiser docs (Studio and iOS pages) and the Flutter fixture (native-test-apps/flutter) pin bonsoir: 6.0.2. On 2026-10-11 the latest release, bonsoir 7.1.5, did not build for Android: bonsoir_android 7.1.3 failed with Unresolved reference 'hostname' in BonsoirService.kt against the Android SDK platform 36 that was installed at the time. bonsoir 6.0.2 built for iOS (profile, no codesign) and Android (profile) with the same advertiser code. The pin stays until a newer bonsoir builds on both platforms.
What to test
- Use the newest Android SDK platform available. Record its API level, plus the Android Gradle Plugin and Kotlin versions used by
native-test-apps/flutter/android. - In
native-test-apps/flutter/pubspec.yaml, changebonsoirto 7.1.5 (or the newest 7.x), runflutter pub get, then runflutter build apk --profile --dart-define=PROBE_AGENT=true --dart-define=PROBE_WIFI=true. Expected: the build succeeds. - Same change for iOS:
flutter build ios --profile --no-codesign --dart-define=PROBE_AGENT=true --dart-define=PROBE_WIFI=true. Expected: the build succeeds with the fixture's deployment target (bonsoir needs at least 13.0). - Run
flutter analyze lib/probe_advertiser.dart. bonsoir 7.0.0 is marked breaking in its changelog (it renames the service host field), so confirm the advertiser still compiles unchanged (initialize(),start(),stop()). - On a physical device in WiFi mode, check that the service is advertised (
dns-sd -B _flutterprobe._tcp local.) and that Studio's WiFi overlay lists the device.
If everything passes
Open a PR that moves the pin in the fixture and in the docs to the new version, removes the "7.1.x was not tried further" note from website/src/content/docs/tools/studio.md, and adds a CHANGELOG entry.
If it fails
Comment here with the exact error, the Android SDK platform, the Gradle and Kotlin versions and the bonsoir_android version. Keep the 6.0.2 pin.
Refs #379.
- Dominant language
- Go
- Stars
- 6
- Forks
- 3
- Avg merge
- 6h 28m
- Merged PRs (30d)
- 362
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainers usually reply within 1 day
-
area/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
AlphaWaveSystems/flutter-probe#424 ·
Maintainers usually reply within 1 day
-
area/docs documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AlphaWaveSystems/flutter-probe#409 ·
Maintainers usually reply within 1 day
-
Dial timeout error should say how long it waited and name the timeout settingPossibly taken @jay23606 claimed this 2 days ago. Openarea/cli bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AlphaWaveSystems/flutter-probe#408 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
AlphaWaveSystems/flutter-probe#888 ·
Maintainers usually reply within 1 day
All issues in AlphaWaveSystems/flutter-probe
Similar issues
-
agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jordansmall/spindrift#7254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pg-sharding/spqr#3275 ·
Maintainers usually reply within 1 day
-
create_or_update_file rejects explicitly empty file contentPossibly taken @Elon-Jiang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/github-mcp-server#3883 ·
Maintainers usually reply within 4 days
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
databricks/terraform-provider-databricks#6210 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Maintainers usually reply within 2 days