Expo-Build schlägt fehl: Ausführung für Aufgabe „:app:mergeLibDexDebug“ fehlgeschlagen ⇐ Android

[Anonymous]

Ich arbeite an einem Expo – React Native-Projekt und habe beim Erstellen der App Probleme mit diesem Problem. Ich musste die meisten Bibliotheken aufgrund eines Problems mit „react-native-maps“ mit neueren Versionen herunterstufen. Hier ist mein package.json
package.json

Code: Select all

    {
"name": "snjt",
"main": "expo-router/entry",
"version": "1.0.0",
"scripts": {
"start": "expo start",
"reset-project": "node ./scripts/reset-project.js",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "expo start --web",
"lint": "expo lint"
},
"dependencies": {
"@expo/server": "^0.7.5",
"@expo/vector-icons": "^14.1.0",
"@react-navigation/bottom-tabs": "^7.4.0",
"@react-navigation/elements": "^2.6.3",
"@react-navigation/native": "^7.1.8",
"expo": "53.0.23",
"expo-constants": "~17.1.7",
"expo-dev-client": "~5.2.4",
"expo-font": "~13.3.2",
"expo-haptics": "~14.1.4",
"expo-image": "~2.4.1",
"expo-linking": "~7.1.7",
"expo-router": "~5.1.7",
"expo-splash-screen": "~0.30.10",
"expo-status-bar": "~2.2.3",
"expo-symbols": "~0.4.5",
"expo-system-ui": "~5.0.11",
"expo-updates": "~0.28.17",
"expo-web-browser": "~14.2.0",
"react": "19.0.0",
"react-dom": "19.0.0",
"react-native": "0.79.6",
"react-native-gesture-handler": "~2.24.0",
"react-native-maps": "1.20.1",
"react-native-reanimated": "~3.17.4",
"react-native-safe-area-context": "5.4.0",
"react-native-screens": "~4.11.1",
"react-native-svg": "15.11.2",
"react-native-web": "^0.20.0",
"react-native-worklets": "0.5.1",
"use-auto-focus-inputs": "^0.1.4",
"zustand": "^5.0.8"
},
"devDependencies": {
"@types/react": "~19.0.10",
"babel-plugin-react-compiler": "^1.0.0",
"eslint": "^9.25.0",
"eslint-config-expo": "~9.2.0",
"eslint-config-prettier": "^10.1.8",
"eslint-plugin-prettier": "^5.5.4",
"prettier": "^3.6.2",
"typescript": "~5.8.3"
},
"private": true
}

Ich habe versucht, den Build lokal auszuführen und habe das gleiche Problem erhalten. Hier sind die Protokolle vom lokalen Build:


Weiß jemand, wie man dieses Problem löst?