React Face Liveness component in iOS 15.x all browser occurred websocket errror, component version 2.0.11

[yoruponder]

Before creating a new issue, please confirm:

• [X] I have searched for duplicate or closed issues and discussions.
• [X] I have tried disabling all browser extensions or using a different browser
• [X] I have tried deleting the node_modules folder and reinstalling my dependencies
• [X] I have read the guide for submitting bug reports.

On which framework/platform are you having an issue?

React

Which UI component?

Liveness

How is your app built?

Create React App

What browsers are you seeing the problem on?

Chrome, Safari

Which region are you seeing the problem in?

ap-northeast-1

Please describe your bug.

user can not connect aws websocket, and throw this error, via sentry we collection this information

in user side they show this dialog

here is sentry tag

User-Agent Mozilla/5.0 (iPhone; CPU iPhone OS 15_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Mobile/15E148 Safari/604.1

What's the expected behaviour?

iOS user can use liveness service normally

Help us reproduce the bug!

when use the iOS 15.x device run liveness component in browser may reproduce the error

Code Snippet

<FaceLivenessDetector
          sessionId={createLivenessApiData ? createLivenessApiData.sessionId : ''}
          region="ap-northeast-1"
          onAnalysisComplete={handleAnalysisComplete}
          disableInstructionScreen={disableInit}
          onUserCancel={() => {
            setLoading(true);
            userCancel();
          }}
          onError={(error) => {
            // -------------------- I send component error to sentry write here --------------------
            console.log('<FaceLivenessDetector>', error)

            if(uid){
              Sentry.setTag("uid", uid);
            }
            
            Sentry.setTag("component", "FaceLivenessDetector");
            let sentry_context = {
              uid,
              type: 'component',
              client,
              access_token,
            }
            if(createLivenessApiData){
              sentry_context.session_id = createLivenessApiData ? createLivenessApiData.sessionId : '';
            }
            Sentry.setContext("Custom-error", sentry_context);
            Sentry.captureException(error);
            Sentry.captureMessage(`<FaceLivenessDetector>-${error.state}`);
          }}
       .....
     />

Additional information and screenshots

user devices

[esauerbo]

Hi @yoruponder, are you also seeing this error with the latest version of @aws-amplify/ui-react-liveness?

[yoruponder]

Hi @esauerbo , I found v3 version react-liveness UI had change, maybe some unknow api also been change, I couldn't update react-liveness to v3 by myself, need to contact and confirm with other team member, it's not easy things 😞, Is it v2 version fix this problem？

[yoruponder]

v3 react-liveness components prop did not have customization Instructions, react-liveness docs also change, and could not find v2 docs, our product need this api to tell user be ready for face check😅😅

[esauerbo]

Hi @yoruponder, thanks for your patience. So we can try to reproduce your error, which exact version of @aws-amplify/ui-react-liveness are you currently using?

Our migration guide has more information on upgrading to the latest version, and if you encounter any issues we're happy to help.

[yoruponder]

Hi @esauerbo, thank you for response. I saw sentry it still occur this error, our @aws-amplify/ui-react-liveness version is 2.0.11

Their devices totally are iPhone, and error from 861184 change to 1721344

Our team has no plan to Upgrading @aws-amplify/ui-react-liveness in the near future 😂

[yoruponder]

react-liveness
├── @aws-amplify/[email protected] -----------------> 2.0.11
├── @babel/[email protected]
├── @sentry/[email protected]
├── @testing-library/[email protected]
├── @testing-library/[email protected]
├── @testing-library/[email protected]
├── [email protected] -------------------> 5.3.7
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[reesscot]

Hi @yoruponder, There was a change made on the service side that should have resolved this issue. Can you please let us know if you are still seeing this issue?

[yoruponder]

Hi @reesscot , In sentry console, It seen like never occur this error again. Thank you!!

[reesscot]

@yoruponder So glad to hear that, and thank you for letting us know! I'll close this out now.