Scan Area and button appear twice

[Mhussein27]

Describe the bug
Select Camera and Start Scanning button appears twice and when I click stop scanning to both buttons, I received the below error :

To Reproduce
Steps to reproduce the behavior:

1. in chrome After giving Camera permission and start first scan , you will see twice Start Scanning
2. Click on 'stop Scanning' first button
3. Click on 'Start Scanning' second button
4. NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Expected behavior
only one scan Area and button should appear

Screenshots

Desktop (please complete the following information):

• OS: [MAC]
• Browser [chrome,]
• Version [Version 108.0.5359.124 (Official Build) (arm64)]

Additional context
Add any other context about the problem here.

[mebjas]

Can you provide me with a working example of how I can reproduce this?

A code example would also do.

[Caitlin-Finn]

@Mhussein27 what framework are you using? If you are using the latest react, this might be due to they way the DOM is rendered in the latest version.

[Mhussein27]

Please close the issue, I managed to fixed, it seems that there was a tag that forcing render twice, once I removed it works fine

…

On Mon, Feb 27, 2023, 6:44 PM Caitlin Finn ***@***.***> wrote: @Mhussein27 <https://github.com/Mhussein27> what framework are you using? If you are using the latest react, this might be due to they way the DOM is rendered in the latest version. — Reply to this email directly, view it on GitHub <#668 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGCAPGHVZDFEUSMVQ6YZXXLWZTKWVANCNFSM6AAAAAATVPC6PM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Lobana-sky]

@Mhussein27 how did you manage that, can you provide the code, please?

[onurerden]

@Mhussein27 1 year later, we got same error message. Can you explain us how did you solved it?

[Mhussein27]

Hi, After I removed this tag </React.StrictMode> my issue has been resolved Good luck with solving the issue Thanks, Maha

…

On Tue, Jun 4, 2024, 11:31 AM Onur Erden ***@***.***> wrote: @Mhussein27 <https://github.com/Mhussein27> 1 year later, we got same error message. Can you explain us how did you solved it? — Reply to this email directly, view it on GitHub <#668 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGCAPGH6ILZAZP6ZZHFXIHTZFV3MRAVCNFSM6AAAAAATVPC6POVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWHEZDKMJVHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>