The developer of the Etiketka mobile application identified a bug that caused a false no-connection error. The issue occurred because the server took longer to process high-resolution photos of product labels than the client was configured to wait.
To resolve the problem, the team implemented image cropping to focus on ingredients, reduced the long side of images to 1600 pixels, and moved the OCR process to a separate thread using asyncio.to_thread. Additionally, the client-side timeout was increased from 20 to 45 seconds.
These technical adjustments ensured that the application successfully reaches the result without triggering premature error messages. The developer noted that such timeouts often mimic network failures when backend processing exceeds client expectations.
