bugstweet 0.9.4

Testers report bugs from inside your Flutter app as GitHub issues an AI coding agent can fix. Tester builds only: store builds never contain it.

0.9.4

• Adds bugstweet_reporter 0.9.4 to tester builds: long shots reach the end of long pages and of lists under a collapsing header or tabs.

0.9.3

• Adds bugstweet_reporter 0.9.3 to tester builds: the preview opens the report screen, Delete on the report screen, and the logo in the tray and on the report screen.

0.9.2

• Adds bugstweet_reporter 0.9.2 to tester builds: the bugsTweet logo as the capture button (the countdowns show over it), and the hosted option.
• Other apps' setups: a relative signing key path in android/key.properties, relative paths in build options (--split-debug-info, --dart-define-from-file, --export-options-plist) and flavor iPhone settings files (Info*.plist) now work in tester builds. After a build without --build-number, a tip says to give tester builds their own.
• init --hosted and .bugstweet/key: send reports through the hosted bugsTweet service with a project key from api.bugstweet.com. The key file is added to .gitignore and put into each tester build; no key in the command.
• The store-build guarantee also checks pubspec.lock, so the reporter is refused when it comes in through a local package or pubspec_overrides.yaml.
• Builds with the Flutter that belongs to the Dart running the tool, so fvm dart run bugstweet uses the FVM version. A missing Flutter gives a clear message instead of a crash.
• Apps in a pub workspace get a clear message instead of a pub error.

0.9.1

• Adds bugstweet_reporter 0.9.1 to tester builds: long shots without overlapping pieces, clips that play on the report screen, the first-launch notice that asks testers before anything is kept, and safer sending and saving.

0.9.0

• Adds bugstweet_reporter 0.9.0 to tester builds: the agent can ask the tester a question, "Fixed in build N, try it", and time travel over the last seconds on the report screen.
• AGENT.md tells the coding agent how to ask the tester a question and how to write "Fixed in build N".

0.8.0

• Adds bugstweet_reporter 0.8.0 to tester builds: app facts (appState) in every report, a scenario in plain words, a repro test that replays the whole path, the phone's condition (network, battery, storage, memory, heat) with a speed test when sent, and long shots of chat screens, tabs and very long pages fixed.

0.7.1

• Adds bugstweet_reporter 0.7.1 to tester builds: privacy fixes, "4 versions" removed.
• run and build refuse a -t / --target option: it would replace the tester file and the build would never start bugsTweet. Change the import in .bugstweet/tester.dart instead.
• build empties the copy's output folder first, so an older build of another flavor or mode cannot sit next to the new one in build/bugstweet.
• Only real build output is left out of the copy: build/ at the root and the platform projects' build/. An app's own assets/build/ or integration_test/build/ is copied.

0.7.0

• Adds bugstweet_reporter 0.7.0 to tester builds: Long shot and Crop.

0.6.0

• Adds bugstweet_reporter 0.6.0 to tester builds: the new "Zomo" look.

0.5.2

• Adds bugstweet_reporter 0.5.2 to tester builds: the springy menu and the sliding tool pill.

0.5.1

• Adds bugstweet_reporter 0.5.1 to tester builds: the glass look.

0.5.0

• Adds bugstweet_reporter 0.5.0 to tester builds: the new Navy look.

0.4.1

• Adds bugstweet_reporter 0.4.1 to tester builds: the tray's Reported list loads 20 reports at a time and can be searched.

0.4.0

• First version of the bugstweet tool. Apps list it under dev_dependencies (flutter pub add --dev bugstweet) and run dart run bugstweet init, run, build apk|appbundle|ipa|ios and clean.
• Tester builds are made in a copy of the app, and bugstweet_reporter (the part testers see) is added to that copy only. This tool has no phone parts and the app never imports it, so store builds contain no part of bugsTweet on Android or iPhone.
• dart run bugstweet run picks a phone, emulator or simulator by itself and never offers desktop or web targets. With none open, it says how to open one.
• The changes of the reporter itself are in bugstweet_reporter's changelog.