Re-check bonsoir 7.x on Android and iOS against a newer SDK; relax the 6.0.2 pin if it builds
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 54/100
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Go
- 星标
- 6
- 派生
- 3
- 平均合并
- 6 小时 28 分钟
- 30 天内合并 PR
- 362
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
AlphaWaveSystems/flutter-probe 的其他 Issue
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree order未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
AlphaWaveSystems/flutter-probe#865 ·
维护者通常 1 天内回复
-
area/cli bug
难度 2/5 1-3 小时 新手友好度 73/100
AlphaWaveSystems/flutter-probe#424 ·
维护者通常 1 天内回复
-
area/docs documentation
难度 2/5 1-3 小时 新手友好度 70/100
AlphaWaveSystems/flutter-probe#409 ·
维护者通常 1 天内回复
-
Dial timeout error should say how long it waited and name the timeout setting可能已有人在做 @jay23606 于 2 天前认领。 未关闭area/cli bug
难度 2/5 1-3 小时 新手友好度 78/100
AlphaWaveSystems/flutter-probe#408 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
AlphaWaveSystems/flutter-probe#888 ·
维护者通常 1 天内回复
查看 AlphaWaveSystems/flutter-probe 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
fluxcd/notification-controller#1441 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
volcengine/volcengine-go-sdk#163 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
OneBusAway/maglev#2145 ·
维护者通常 2 天内回复
-
priority/medium status/ready type/chore
难度 2/5 1-3 小时 新手友好度 84/100
discobox-ai/discobox#1357 ·
维护者通常 1 天内回复