-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Build Fails in React-Native Version 0.52.0 #2493
Comments
I can confirm that upgrading to 0.52.0 breaks the build on android :( |
+1 |
Hey guys, you can check #2494 PR, it supports last React Native version. |
Thanks @Moreno97, will try that locally. Hopefully we can get this merged soon! |
@Moreno97 your PR no longer seems to have any changes :( |
@danilobuerger I know, it was my fault, I put the code on the wrong branch and it was removed. I'm working on it. |
@Moreno97 since it's not going to get merged into v1 anyway, I will glady merge it into my fork here: https://github.com/feastr/react-native-navigation. |
It's finished @danilobuerger , check #2545 . |
@Moreno97 thanks, going to commit it to my fork. |
Any idea how to solve this issue with RN0.52 ?? I am still getting the same error during android build ? |
i have the same problem, i'm going to install RN 0.51 to check wether problem is beacause of version |
Yep, i've installed RN 0.51 and it goes good, it seems the problem is by using RN 0.52 |
Same situation for me |
+1 |
2 similar comments
+1 |
+1 |
+1 😢 |
+1 😭 |
+1 |
Any news? |
wup wup, any ideas how to fix it? |
How about picking up PR changes and integrate it in your project rather than adding up +1s which provides no help and gives the OP unnecessary email notifications? If it's so urgent, JUST DO IT! |
I just downgraded to 0.51 as the project page says it supports up to 0.51. Works. |
@vishal-android-freak Sorry for another unnecessary email notif. Even though I share your feelings, but I can only partially agree. I believe many people don't have the time/resource to do that, and also, patching the PR in many cases only validates things work in basic cases. I might not trust myself with a patched PR without battle tested functionality, and I might not want to push that change to my users, so it would be the best that the professionals - the wix team can prioritize this task. +1 is just a way for pushing prioritization. |
@shivawu while I completely get your point, if you go through the PR, one file has few changes to be done, THAT's IT! You can definitely go ahead with the changes on your side and wait for the official release till then. These changes are not something that are going make your build unstable 😅 |
Well I'm looking through both pull requests and both of them seem to be giving some people some issues. It seems these changes are something that are going to make your build unstable 😌 |
@kk1429 is this good to close now that #2580 has been merged? that PR fixed my instance of the same build error. |
I just upgraded to RN 0.53 and RNN 1.1.370 and everything works fine. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
@kk1429 @vishal-android-freak Did you guys solved it? I am facing the same issue with android |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
The issue has been closed for inactivity. |
Nobody :( |
I am trying to install this library in my project. However, the build is failing, I followed all the install steps but the errors just dont go away.
I think this library might not be compatible with version 52 of react-native. I might be wrong though. I will share my build.gradle files.
app/build.gradle
build.gradle
MainApplication
MainActivity
Build Error
I was using this library in my previous project and I noticed that the react-native version has changed so I am using this is the case. Otherwise any suggestions?
Environment
UPDATE
Just tested on react-native version: 0.51.0 and react: 16.2.0. Everything works !
The text was updated successfully, but these errors were encountered: