Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initialization on iOS take some time #6

Open
Johny8811 opened this issue Apr 20, 2021 · 6 comments
Open

Initialization on iOS take some time #6

Johny8811 opened this issue Apr 20, 2021 · 6 comments

Comments

@Johny8811
Copy link

Hi guys,

this is my implementation of scanner

`export const scanDocument = async () => {
try {
await readLicence();
} catch (error) {
throw error;
}

try {
await setOCRConfig();
} catch (error) {
throw error;
}

try {
return await showScanner();
} catch (error) {
throw error;
}
};`

I call this method in useEffect but scanner will not start on iOS, without any error.

useEffect(() => { scanDocument(); }, []);

I tried add some timeout. 300ms scanner start correctly, below 300ms scanner doesn't work.

Android works correctly, scanner start immediately after component is mounted.

What is wrong??

@vyakimchik
Copy link
Contributor

Hi @Johny8811,

Are you able to successfully start the scanner in our demo project that is available in this repository?

Thanks!

@Johny8811
Copy link
Author

Hi @vyakimchik,

yep, I started it but problem is only only on physical device, on simulator scanner start correctly.

Thanks.

@vyakimchik
Copy link
Contributor

@Johny8811,

Are you experiencing this issue only with one device or with any physical device you have?

@Johny8811
Copy link
Author

Johny8811 commented Apr 21, 2021

I tried it on iPhone 12 pro 14.4 and on another iPhone 12 14.4.2.

@vyakimchik
Copy link
Contributor

I've tried also to run on iPhone 12 pro but didn't notice what you mentioned. Could you please record and send us the video where you demonstrate the reproduction of the issue in our app? You can send the video to [email protected].

Have you changed anything in our demo project to reproduce the issue?

Thanks!

@vyakimchik
Copy link
Contributor

Hi @Johny8811,

Are you still experiencing the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants