bugstweet 0.9.12

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.12

• Tester builds use bugstweet_reporter 0.9.12 (the alive bird, safer answers in the tray, no crash card after swiping the app away, polish).

0.9.11

• Tester builds use bugstweet_reporter 0.9.11 (tray fixes found on a real phone: one popup for several fixes, the answer's Send in sight while typing, the bugsTweet banner, replies inside their report).

0.9.10

• Tester builds use bugstweet_reporter 0.9.10: the crash card after the app closed unexpectedly, and with the hosted service the app's network and printed log, developer replies in the tray, and the clip on reports added to an existing issue.

0.9.9

• Tester builds carry a build receipt: the app's commit, whether it had uncommitted changes, the flavor, the bugstweet version and a fingerprint of the widget list (CX-W1). With the hosted service, paid reports name them so the agent can check out the same code.
• With the hosted service, each tester build also sends the names of the app's Dart files that changed since the previous tester build (names only, never code), so testers' trays can mark reports whose files changed (CX-W3).
• New command dart run bugstweet verify <report> --test <file> (CX-W5, hosted service): after a fix, it runs the bug's test on the code the tester's build was made from (it must fail) and on the code now (it must pass), then posts "Verified fix" with both commits to the report. When the runs do not prove the fix, it says why and posts nothing.
• New free command dart run bugstweet shorten --test <file> (CX-W4): for a failing bug test, it removes taps one at a time and keeps only those the failure needs (the test must still fail the same way), then writes the shortest test next to the original, which stays as it is.

0.9.8

• Adds bugstweet_reporter 0.9.8 to tester builds: one card for several reports fixed in the same build ("9 reports are fixed in this build"), and no cut text where the tester reads (whole titles, every change, typed notes that grow).

0.9.7

• Adds bugstweet_reporter 0.9.7 to tester builds: the tray groups reports by what needs the tester (Ready to retest, Being worked on, Not started, Done folded away) and says which build the phone is on; with the hosted service, the duplicate guard, the agent's cards and "Fixed in build N" are made by the service (paid parts), and fix notes are read the way people write them.

0.9.6

• Adds bugstweet_reporter 0.9.6 to tester builds: "The full issue" shows the pictures exactly as they are sent, and a retry sends the same pictures (CX-W6).
• Hosted builds (with a project key in .bugstweet/key) send the list of the app's widget classes with their file and line to the bugsTweet service at each run and build: names and places, never code. The service writes where each widget is in the code into the project's paid reports. If it cannot be sent, the build goes on and says so (P7, step 3).

0.9.5

• Adds bugstweet_reporter 0.9.5 to tester builds: the logo in any of four presets or your own colors (logoColors in the tester file).
• Safety: making a tester build never changes your app's own files. A link to a file is copied as a real file, and a file reached through a link to a folder elsewhere is not changed: the build stops and says which link to replace. Before, the changes for the tester copy could go through a link into your app (CX-B3).
• -tlib/main_dev.dart and -t=lib/main_dev.dart (the start-file option with its value attached) are refused like -t lib/main_dev.dart. Before, they slipped through and the tester build had no bug button (CX-B2).
• build ios --simulator works: the result is collected from the simulator's own folder, and an older tester build is replaced only when a new one is really there. Before, it looked in the device folder, deleted the previous tester build and stopped with an error (CX-B4).

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.