Scanner stuck after 'Retry' pressed

[karlistts]

Step 1: Are you in the right place?

• For general technical questions, post a question on StackOverflow
  with BlinkID and Microblink tags.

• For issues or feature requests related to the code in this repository
  file a Github issue.

• For help troubleshooting your application that does not fall under one
  of the above categories, reach out to the personalized
  Microblink support.

Step 2: Describe your environment

• Xcode version: 15.3
• BlinkID SDK version: 6.7.1
• What are you trying to scan: any invalid document

Step 3: Describe the problem

1. Get into any of the following error states: document data inconsistent / document sides do not match / capture timed out
2. Tap 'Retry'
3. The scanner gets 'stuck' and doesn't react to any new documents being presented to the camera

Reproducible 100% of the time when encountering any of the above errors.

See video:

RPReplay_Final1715757048-1.mov

Reproduced on the react-native sample app (on iOS only) as well as the iOS demo app from App Store.

Step 4: Relevant code

Using the sample app from blinkid-react-native without any modifications.

[MBrizic01]

Hi @karlistts, Thank you for your report. We are aware of this issue, which will be fixed in our next release, v6.8, planned for late June. We appreciate your detailed analysis. Please follow our releases to be up to date when we deliver a new version containing this bug fix.

[hanwoo-kim]

Hi there,

This issue seems to be still existing on BilnkID 6.8.0.
Please have a look at the screen recording attached.
Thanks.

RPReplay_Final1719183984.2.mp4

[MBrizic01]

Hello @hanwoo-kim, Thank you for reporting, but this looks like a different type of problem as the scanning process is not finished, and the retry button is not pressed. Still, what is shown in the video isn't the expected behavior, so we will investigate it and inform you of our findings.

[MBrizic01]

@hanwoo-kim please update to v6.9.0 as we fixed this in our latest release. Thank you!

[hanwoo-kim]

@hanwoo-kim please update to v6.9.0 as we fixed this in our latest release. Thank you!

Yes, double checked it's fixed on the version.
Thanks!