You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on a project I discovered that it is possible to enter a stage of no progression (seemingly while still processing a lot of data). This from my experience happens if a scan is intiated that has a particularly bad angle or not entirely square document.
After that heavy processing seems to be going on in the background, as the garbage cleaner is going wild (and at least on my tested devices an infinite circular progress indicator is overlayed). Meanwhile the camera feed is still being shown and preview shapes are still drawn correctly. This state never ends and never yields an actual image.
To be sure I didnt mess up and caused this myself, I tried and successfully replicated this behaviour with your example app.
I tested this on two devices. Both running Android 11. Samsung Galaxy M32 and realme 8 Pro. The latter one had the same issue although with lower frequency.
A restart of the app / state reset fixed the issue.
Im a little short on time right now, but if it would be still helpful then I could provide screen-capture footage of this issue in a few weeks.
The text was updated successfully, but these errors were encountered:
While working on a project I discovered that it is possible to enter a stage of no progression (seemingly while still processing a lot of data). This from my experience happens if a scan is intiated that has a particularly bad angle or not entirely square document.
After that heavy processing seems to be going on in the background, as the garbage cleaner is going wild (and at least on my tested devices an infinite circular progress indicator is overlayed). Meanwhile the camera feed is still being shown and preview shapes are still drawn correctly. This state never ends and never yields an actual image.
To be sure I didnt mess up and caused this myself, I tried and successfully replicated this behaviour with your example app.
I tested this on two devices. Both running Android 11. Samsung Galaxy M32 and realme 8 Pro. The latter one had the same issue although with lower frequency.
A restart of the app / state reset fixed the issue.
Im a little short on time right now, but if it would be still helpful then I could provide screen-capture footage of this issue in a few weeks.
The text was updated successfully, but these errors were encountered: