Using UNSAFE_componentWillUpdate in strict mode is not recommended and may indicate bugs in your code.

[ngoctan3006]

I'm experiencing a similar issue as shown in the image below, and here are the dependencies I'm using:

"dependencies": {
    "@crello/react-lottie": "^0.0.11",
    "@reduxjs/toolkit": "1.9.5",
    "antd": "5.4.6",
    "axios": "0.21.4",
    "prop-types": "15.8.1",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-icons": "4.8.0",
    "react-lottie": "1.2.3",
    "react-redux": "8.0.5",
    "react-router-dom": "6.10.0"
  },
  "devDependencies": {
    "@types/node": "18.16.2",
    "@types/react": "18.0.28",
    "@types/react-dom": "18.0.11",
    "@types/react-lottie": "1.2.6",
    "@vitejs/plugin-react": "3.1.0",
    "prettier": "2.8.8",
    "sass": "1.62.1",
    "typescript": "4.9.3",
    "vite": "4.2.0"
  }

WARNING: Using UNSAFE_componentWillUpdate in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
Please update the following components: Lottie2