Device orientation incorrectly detected

[szegadal]

Before creating a new issue, please confirm:

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

On which framework/platform are you having an issue?

React

Which UI component?

react-liveness

How is your app built?

Vite

What browsers are you seeing the problem on?

No response

Which region are you seeing the problem in?

No response

Please describe your bug.

The user is experiencing issues starting the liveness session. The component is incorrectly detecting the device orientation, preventing the session from starting.

What's the expected behaviour?

The session should start as expected (Several successfull cases)

Help us reproduce the bug!

I can't reproduce. The device is apparently an Iphone (see picture attached)

Code Snippet

No response

Console log output

{ state: MOBILE_LANDSCAPE_ERROR, error: null }

Additional information and screenshots

[cwomack]

@szegadal, can you share your package.json so we can see the versions of dependencies as well as how the customer/user who experienced this is able to reproduce? We may need a little more information to reproduce this and figure out what's happening.

[szegadal]

Yes of course!

{
  "name": "biometrico",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "env-cmd -f .env.dev vite",
    "build:test": "env-cmd -f .env.test npm run build && firebase deploy --project=test --only hosting:test",
    "build:prod": "env-cmd -f .env.prod npm run build && firebase deploy --project=prod --only hosting:prod",
    "build": "vite build",
    "lint": "eslint .",
    "preview": "vite preview"
  },
  "dependencies": {
    "@aws-amplify/ui-react": "^6.5.0",
    "@aws-amplify/ui-react-liveness": "^3.1.10",
    "@radix-ui/react-icons": "^1.3.0",
    "@radix-ui/react-slot": "^1.1.0",
    "aws-amplify": "^6.6.2",
    "class-variance-authority": "^0.7.0",
    "clsx": "^2.1.1",
    "firebase": "^10.13.2",
    "lucide-react": "^0.453.0",
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "react-responsive-modal": "^6.4.2",
    "react-router-dom": "^6.27.0",
    "sonner": "^1.5.0",
    "tailwind-merge": "^2.5.4",
    "tailwindcss-animate": "^1.0.7"
  },
  "devDependencies": {
    "@aws-amplify/backend": "^1.3.0",
    "@aws-amplify/backend-cli": "^1.2.8",
    "@eslint/js": "^9.9.0",
    "@types/react": "^18.3.3",
    "@types/react-dom": "^18.3.0",
    "@vitejs/plugin-react-swc": "^3.5.0",
    "autoprefixer": "^10.4.20",
    "env-cmd": "^10.1.0",
    "eslint": "^9.9.0",
    "eslint-plugin-react": "^7.35.0",
    "eslint-plugin-react-hooks": "^5.1.0-rc.0",
    "eslint-plugin-react-refresh": "^0.4.9",
    "globals": "^15.9.0",
    "postcss": "^8.4.47",
    "tailwindcss": "^3.4.14",
    "vite": "^5.4.1"
  }
}

I should mention that is an unique case between 30+ validations since we launch it into production (last friday)

[cwomack]

@szegadal, can you see if upgrading your @aws-amplify/ui-react-liveness version to 3.1.19 (the latest version) results in a difference of behavior? Also, do you know what type of devices (model, iOS version, etc) the customers are experiencing this on?

I think we'll need more details on how to reproduce this to better understand what is going on.