aws-amplify
Amplify Liveness intermitently does not ask for Camera Permission on FireFox mobile (iOS & Android)
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?
Vite
What browsers are you seeing the problem on?
Firefox
Which region are you seeing the problem in?
us-east-1
Please describe your bug.
Sometimes the package does not ask for camera permission on Firefox mobile, and keep on an infinite loop displaying the waitingCameraPermissionText.
Please note that it is intermittent, sometimes works, sometimes does not but it fails in most cases. It works fine on Firefox for desktop and other browsers, the issue is only on Firefox mobile.
What's the expected behaviour?
We should see a pop up requesting the camera access permission or display the component on the screen.
Help us reproduce the bug!
- Create a vite react app
- Install amplify liveness as described in the documentation
- Use the example provided in the documentation to create a sessions ID
Code Snippet
// Put your code below this line.
import React, { useEffect, useState } from "react";
import { FaceLivenessDetector } from "@aws-amplify/ui-react-liveness";
import { Loader, ThemeProvider, Button, Flex } from "@aws-amplify/ui-react";
import CancelIcon from "../components/icons/CancelIcon";
import CheckIcon from "../components/icons/CheckIcon";
import { API_URL } from "../data/constants";
import { FaceLivenessDictionary } from "../data/translations";
import { useTranslation } from "react-i18next";
import { extractLanguageCode } from "../utils/common";
const FaceLiveness = ({ handleNextStep, dispatch, acessToken }) => {
const { t, i18n } = useTranslation();
const [language, setLanguage] = useState("");
const [loading, setLoading] = useState(true);
const [createLivenessApiData, setCreateLivenessApiData] = useState(null);
const [result, setResult] = useState({
completed: false,
ok: false,
});
const handleError = (error) => {
dispatch({
type: "awsLivenessError",
value: error,
});
};
const fetchCreateLiveness = async () => {
try {
const response = await fetch(`${API_URL}/create_face_liveness_response`, {
headers: new Headers({
Authorization: `Bearer ${acessToken}`,
}),
});
const json = await response.json();
setCreateLivenessApiData(json);
setLoading(false);
} catch (error) {
handleError({
state: "SERVER_ERROR",
message: "Failed to fetch when createliveness",
});
}
};
useEffect(() => {
const language = i18n.language;
setLanguage(extractLanguageCode(language));
fetchCreateLiveness();
}, []);
const handleSuccess = (data) => {
setResult({
completed: true,
ok: true,
});
dispatch({ type: "awsLiveness", value: data });
setTimeout(() => {
handleNextStep();
}, 2000);
};
const handleFailure = () => {
setResult({
completed: true,
ok: false,
});
fetchCreateLiveness();
setTimeout(() => {
setResult({
completed: false,
ok: false,
});
}, 2000);
};
const fetchApi = async () => {
try {
const response = await fetch(
`${API_URL}/get_face_liveness_response/${createLivenessApiData.SessionId}`,
{
headers: new Headers({
Authorization: `Bearer ${acessToken}`,
}),
}
);
return response;
} catch (error) {
handleError({
state: "SERVER_ERROR",
message: "Failed to fetch when getting liveness",
});
return false;
}
};
const handleResponse = async (response) => {
const data = await response.json();
return data;
};
const handleAnalysisComplete = async () => {
const response = await fetchApi();
if (!response) {
handleFailure();
return;
}
const data = await handleResponse(response);
if (data.Confidence < 75) {
handleFailure();
} else {
handleSuccess(data);
}
};
const handleRetry = () => {
fetchCreateLiveness();
setLoading(true);
setTimeout(() => {
setLoading(false);
}, 1000);
};
return (
<div className="w-full flex flex-col align-center justify-between flex-grow text-center lg:px-20 z-10">
{result.completed ? (
<>
<p className="text-lg md:text-xl">{t("result")}</p>
{result.ok ? (
<>
<CheckIcon />
<p className="text-lg md:text-xl">{t("redirectMessage")}...</p>
</>
) : (
<>
<CancelIcon />
<p className="text-lg md:text-xl">{t("retryMessage")}...</p>
</>
)}
</>
) : loading ? (
<Loader className="self-center" />
) : (
<ThemeProvider>
<FaceLivenessDetector
sessionId={createLivenessApiData.SessionId}
region="us-east-1"
onAnalysisComplete={handleAnalysisComplete}
displayText={FaceLivenessDictionary[language]}
onError={handleError}
components={{
ErrorView: ({ children }) => {
return (
<Flex
justifyContent="center"
alignItems="center"
width="100%"
height="100%"
>
<Flex
backgroundColor="white"
direction="column"
justifyContent="center"
padding="32px"
>
{children}
<Button
maxWidth="120px"
alignSelf="center"
onClick={handleRetry}
>
{t("retry")}?
</Button>
</Flex>
</Flex>
);
},
}}
/>
</ThemeProvider>
)}
</div>
);
};
export default FaceLiveness;
Console log output
No console error, the request to create the session ID is OK.
Additional information and screenshots
@paternina What version of Firefox mobile are you using and what's your OS version?
@paternina What version of Firefox mobile are you using and what's your OS version?
Is Firefox Mobile 130.0.1 and we used iOS 18 but we have the same behavior in Android 13
When you say FireFox Mobile, you mean Firefox for iOS and Firefox for Android, right?
We have the following:
"@aws-amplify/ui-react": "^6.5.1", "@aws-amplify/ui-react-liveness": "^3.1.11", "aws-amplify": "^6.6.2"
Hi @Tyg0th, I'm unable to reproduce this issue using iOS 18 and Firefox 130.1. The browser is correctly prompting me for permissions on every load of the component.
Any other patterns of when this happens you can think of that might help us narrow this down?
@Tyg0th are you using http by any chance? Some browsers will block camera and microphone access on insecure origins. You could try printing navigator.mediaDevices to the console; if it's undefined it likely means camera access is blocked.
Hi @reesscot it fails intermittently sometimes ask for permissions and sometimes it does not, the only difference from our code and the one shared in the documentation is that we are using a check camera utility function before showing the component
useEffect(() => {
const checkCamera = async () => {
const cameraExist = await detectWebcam();
setDeviceHasCamera(cameraExist); // if false show an error message and does not load the component
};
checkCamera();
}, []);
This is just a JavaScript function that check if customer have a camera.
export const detectWebcam = async () => {
let md = navigator.mediaDevices;
if (!md || !md.enumerateDevices){
return false;
}
try {
const devices = await md.enumerateDevices();
return devices.some(device => device.kind === "videoinput");
} catch (error) {
console.error('Error enumerating devices: ', error);
return false;
}
};
It may responde your question @esauerbo , we are using https and we check the cameras using the above function.
As you may noticed, the FaceLivenessDetector component is loaded and is always showing the waitingCameraPermissionText script.
@paternina just for reference, we perform a similar check in the component to make sure that a customer has a valid video devices - https://github.com/aws-amplify/amplify-ui/blob/main/packages/react-liveness/src/components/FaceLivenessDetector/service/machine/machine.ts#L961
However we also have a simple check for virtual cameras as the Rekognition services want to avoid the usage of virtual cameras when possible to help avoid fraud.
Hi @thaddmt
Thank you for the reference!
I’d like to clarify my understanding: it seems that this implementation only checks if the user has a virtual camera device and then throws an error. The error returned should be handled by the onError?: (livenessError: LivenessError) => void; method from the FaceLivenessDetectorCoreProps interface. If that's the case, we should be able to catch it in the dispatch, set it in the state, and the component should display a different error message on the screen rather than the one requesting permission, correct?
Additionally, please note that the FaceLivenessDetector component is being displayed but is always showing the "waiting for camera permission" text, so I am not sure if the issue is related to the detectCamera function.
To provide more context, the main issue we're encountering is that when customers visit our site for the first time using Firefox for Android and Firefox for iOS, it correctly requests camera access, and everything works as expected. However, on subsequent visits (the second or third time), the component fails to load even though permissions are granted. Currently, the only workaround is to clear all site permissions and start fresh.
@paternina the component throws an error if there are only non virtual cameras available, but it also checks for a few other constraints like frame rate and video width/height. Otherwise that's correct.
Are you still able to reproduce this behavior if you remove the detectWebcam logic? If so would you be able to share a reproduction repository with us?
Hi @esauerbo
Unfortunately I cannot share a public repository, it is a private work and company does not allow us to share it, but, the component is exactly like shared above, and I also shared the detectWebcam logic. I removed the detectWebcam logic and the issue persist, it request access to camera once, but subsequent visits do not request it.
@paternina Can you share what you are using in the screenshot to debug?
Are you using the camera anywhere else in your app which might be preventing the Liveness component from using it? In the screenshot I see the log message "Stopping active stream on Back Triple Camera". The Liveness component doesn't support using the back cameras, on the forward/user facing cameras.
Hi @reesscot , yes we use a component to capture the user document (KYC flow) before the liveness process, it uses another package and a custom fallback option when customer device does not meet the minimum requirements for the first one. However, this step is completed successfully and then pass to LivenessDetector.
@paternina That's good information, thanks for sharing. My suspicion is that your other component is not releasing the video stream, which is causing the Liveness component to be unable to access the camera. Can you try replacing the Liveness component with a getUserMedia call using the Liveness default constraints?
@paternina, wanted to circle back and see if you tried the suggestion above. Let us know if you've had a chance to replace the Liveness component with a getUserMedia call using the Liveness default constraints?
Hi @cwomack & @reesscot
We have had a similar issue reported by a client. They are using Firefox version 133.0.2, Android version 14, Samsung Galaxy A53. When they switch over to Chrome it works as expected.
When the user loads the liveness page there is no prompt asking to use the camera. We get the below error
error: {
"state": "CAMERA_ACCESS_ERROR",
"error": {}
}
And the UI defaults to:
Manually changing the camera permissions (and all other media permissions) for our website to allowed, we see the same issue.
Using BrowserStack to test on different devices, we can replicate the issue on additional devices, a Samsung A51, A52 using Firefox (stopped testing on other Samsung devices at this point).
Looking at your above mentioned recommendations of using getUserMedia call using the Liveness default constraints in place of the liveness component, we can see that there is no prompt asking for camera permissions when using Firefox on a Samsung A52 device. Changing the Liveness default constraints to something like { audio: false, video: true } the prompt to request camera permissions works as expected for Firefox on the A52 device.
Testing liveness on Firefox on my device, Android 14, Samsung Galaxy S23 Ultra it works as expected (additionally the getUserMedia query with the Liveness default constraints works) and I get the prompt to enable camera permissions, the issue seems to be related to the model of the mobile.
Using:
"@aws-amplify/ui-react-liveness": "^3.1.18",
"aws-amplify": "^6.10.2"
Let me know if you require any more details to look into this issue further for us, thanks
@gary-hodgson-infotrack, thanks for the testing and response here. It may be that this is a Firefox specific issue, but we're going to try and reproduce this internally and follow up.
@gary-hodgson-infotrack, thanks for the testing and response here. It may be that this is a Firefox specific issue, but we're going to try and reproduce this internally and follow up.
@cwomack do you have any updates on this issue raised by Gary from our team. The client has reached out that this is still an issue with the specific firefox version on the device Android version 14, Samsung Galaxy A53.
@swathimaddali-infotrack, thanks for the additional info from the client. Is there a way to confirm if this is experienced on later version of Firefox as well? Or has this been pinned down to only occur with this specific version (or specifically the combination of the Firefox version and the Android device)? Trying to see if this is isolated to that combo or if it's impacting other devices outside the Samsung A52/53's. Basically, want to ask either you or the client to use the latest version of Firefox and confirm if the behavior continues.
@cwomack Just to add some more information. We tried using android studio - virtual device with same exact firefox version and Android 14, and it works great. But unfortunately we cannot get the Samsung A series to test directly. I wonder whether that's device specific issue or not.
@IvanWijayaInfoTrack and anyone else following this thread, thank you for the additional information. We're investigating this issue and looking for ways to be able to reproduce this on our end. We'll be sure to follow up with another comment if we can identify the root cause.
Hello @IvanWijayaInfoTrack, @swathimaddali-infotrack, @gary-hodgson-infotrack, we were able to reproduce the issue on a Samsung A51 and have discovered the root cause of the issue. It was caused by the max frame rate constraint we enforce on the camera, causing Firefox to incorrectly assume that camera permissions were not allowed.
We've increased the frame rate as a potential fix for this in @aws-amplify/[email protected], and have confirmed that the Samsung A51 is able to access camera permissions with this change. Please upgrade and let us know if this release solves this issue for you, thanks!
As we haven't heard back from you in a while and the fix has been released, I'm going to close this issue for now. If you're still experiencing problems with camera permissions on Firefox/Android, please let us know and we'll re-open and follow up with you. Thank you!