-
Notifications
You must be signed in to change notification settings - Fork 903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@react-native-community/cli-platform-android Build Failed: The current character read is 'i' with an int value of 105 #1981
Comments
FYI this StackOverflow is very similar to my issue but it is nearly 4 years old so may vary slightly. I have tried following it but if anyone can help explain or point me to more possible solutions that would be great. |
i'm experiencing the same issue since upgrading a dependency. I've also tried a clean install, downgrading the dependencies, further upgrading them but i can't the app running. (Can also confirm this on various apps) |
When did this error start for you? I've tried rolling back to previous commits and re-cloning to an earlier version of the app I'm still facing the same error. Could you talk me through you clean install process please? |
It seems like this issue is related with the latest cli release which came with the release of react native 0.72 yesterday. Problems occurred since then for me. |
I am also facing this issue with no solution |
Im also facing the same issue... is there any fix yet for this ? Thanks |
me to. Suddenly this error appeared. |
Guys i have found a workaround, we changed 3 things
|
same issue here, it only works when I do delete node_modules and yarn install again but the error will appear again if I run the second build (yarn react-native run-android), which means I must delete node_modules and yarn install again every single time I want to develop/build the app. I found this issue when i add react-native-cameraroll I've already tried it on my both device which is Windows 11 and MacOS Ventura 13.3.1 and the issue is still the same |
Same. Impossible. Changed so many versions. It is everywhere, it does not depend on packages that you have at all. |
Already fixed here |
I don't understand how or why, but I removed "react-native-image-picker": "^5.0.1" and it started to build again. How got to removing this package:
I wasn't returning JSON.
And that revealedan error that there was something missing in the AndroidManifest.xml of the react-native-image-picker package.
I don't understand why this happened, it was done through ALOT of trial and error but it worked. Hope this helps someone |
Yeah and then try to build again. It will fail |
So how it fixed ? |
me too. |
Hello 👋 This is probably not issue related to React Native CLI - but related to libraries, please try upgrading (such as react-native-image-picker or react-native-cameraroll or any other) - probably in these libraries were introduced breaking change that breaks your app. Please also try creating fresh React Native app with |
yarn remove react-native-image-picker |
After discussing this issue with @cortinico, the problem is with broken backward compatibility in libraries, right now for this we have two solutions:
We'll upstream fixes for this to the older versions (0.69, 0.70) of RN soon. |
I use react native |
Hey @fahmiabdulyakub, you must check in your Note: You should have fix for that as you're using |
I still confuse about that solution. This my
|
You shouldn't have Edit: also you shouldn't have
|
@szymonrybczak something to add to #1983 ? |
Good idea! |
For me it was caused by |
1.rm -fr node_modules |
npx react-native run-android --variant=devDebug FAILURE: Build failed with an exception.
BUILD FAILED in 2s error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup. FAILURE: Build failed with an exception.
BUILD FAILED in 2s
info Run CLI with --verbose flag for more details. C:\Users\nhung\Desktop\soba\src\Soba-MobileApp>./gradlew clean C:\Users\nhung\Desktop\soba\src\Soba-MobileApp>cd android C:\Users\nhung\Desktop\soba\src\Soba-MobileApp\android>./gradlew clean C:\Users\nhung\Desktop\soba\src\Soba-MobileApp\android>gradlew clean FAILURE: Build failed with an exception.
BUILD FAILED in 5s |
hey @nhokmoon, make sure that |
@nhokmoon , did you fix the issue? i've been stuck for days now. |
Does RN work with PNPM nowadays? It didn't use to. |
Hello! In - <manifest xmlns:android="http://schemas.android.com/apk/res/android">
+ <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.reactnativeimageresizer"> And the value of I know that making changes directly in the Related to the node module:Even though I raised a PR #399, I don't think that it is going to change in the module, since it was a change introduced in React Native 0.73 (react-native-community/discussions-and-proposals/issues/671) |
I found the solution to RN cli issues specifically for older RN versions as pointed by @nhokmoon. I am using RN 68.7. I added "resolutions": {
"@react-native-community/cli": "^7.0.0",
"@react-native-community/cli-config": "^7.0.0",
"@react-native-community/cli-debugger-ui": "^7.0.0",
"@react-native-community/cli-doctor": "^7.0.0",
"@react-native-community/cli-platform-android": "^7.0.0",
"@react-native-community/cli-platform-ios": "^7.0.0",
"@react-native-community/cli-server-api": "^7.0.0",
"@react-native-community/cli-tools": "^7.0.0",
"@react-native-community/cli-types": "^7.0.0"
} And now the Android build is succeeding 🚀. Check the compatible version of RN CLI version for your RN version: https://github.com/react-native-community/cli?tab=readme-ov-file#compatibility |
thanks i will try it |
Im Using 0.73 Facing Same Issue, but I also some more |
Hello, get same exception after upgrde to new version (0.74) of RN.
In my case the problem was an old I copied gradlew.bat from blank project, and this issue moved away. You may create reference project from last RN with command P.S. |
OS: Windows 10 Hey guys, This might not be the place to write this, but this is the issue that was closest to the problem I was facing. I am currently trying to integrate react-native-auth0 to my Expo project. My current dependencies are:
I'm running Java 17 and Gradle 7.3 (which is what I need to use according to the compatibility matrix. The Auth0 library only runs with native code. So when trying to build the Android native code using the Expo builder, i.e. `npx expo run:android FAILURE: Build failed with an exception.
BUILD FAILED in 969ms I get the same result when changing directory (cd) to the This is the code in my
Any help would be appreciated. Please let me know if any other information is needed. For more context, this is the repository and branch I am working on https://github.com/lnaidu14/quickpay/tree/19-integrate-auth0 |
Hi, were you able to upstream the fix for .69? |
我也有这个问题,想问下怎么解决的 |
@captainalbert did you find a solution for |
Yes. What I do whenever I encounter this are the ff steps:
and the project will run fine again in my case. |
I Have the same issues, |
I'm able to fix my case. i run npx react-native config to see the exact issue that i was facing and saw |
The solution is |
Having same problem on 0.74.5 |
I have this problem on 0.75.4 BUİLD FAILED in 331ms
I thought the issues would be similar. Is there any solution? |
same with react-native-maps
|
same issue |
anyone solved it with rn70.8 |
I was building, running and demoing my app at 11:30am this morning using npx react-native run-android, I made a PR and merged my branch into Dev an hour later. The build failed with the error below. I thought this was odd so in my local I deleted node_modules and package-lock.json, ran cd android && ./gradlew clean, then cd.. and npx react-native run-android. My local started producing this same error. I have no idea what could have changed or what would have caused this.
I have been googling and trying different solutions with no success and a deadline looming. Can anybody help guide me to a solution please? TIA!
Environment
react-native info
Description
npx react-native run-android
The text was updated successfully, but these errors were encountered: