-
-
Notifications
You must be signed in to change notification settings - Fork 227
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 failed. Error cannot find symbol builder.setNavigationBarColor #279
Comments
Any updates about this issue? |
yeah, luckily somebody point this up..having this issue with react native version 0.64... |
Please update Android Gradle, any pull request is welcome! 🙂 |
Sorry guys, are you using Android Support instead of AndroidX? 🤔 |
I'm using the androidX |
these are the details of gradle which I use currently android/build.gradle
android/gradle/wrapper/gradle-wrapper.properties |
What Android versions are you testing? Happy week! ❤️ |
i've run into your code (project example) and it's similar to my previous react native version (0.63.3). In this version, the app is working fine and able to run...the build error happened after I upgrade to version 0.64.2... i am using android API 29...let me know if u need further info... |
Do you have this configuration? facebook/react-native#25787 (comment) Thanks for your collaboration! 👍 |
Facing the same issue with React native 0.61.4. It was working fine 2 days ago. |
this is a fresh init project version 0.64.2...it went to error as soon as i npm install this library...here is the link of the sample project https://github.com/mattop1709/agorgy |
I just updated example project to the RN version 0.64.2, working as expected in my machine https://github.com/proyecto26/react-native-inappbrowser/tree/develop/example Can you try updating your Android Studio/SDK? We added new configuration required to support Android 11 :) |
Thanks for sharing! I found the issue here: https://github.com/mattop1709/agorgy/blob/main/android/build.gradle#L10 Try using recent versions of AndroidX libraries (androidx.browser:browser):
Let me know if you have any other questions 👍 |
Oh and on the other hand, with Autolinking you don't need to install this package manually :) https://github.com/mattop1709/agorgy/blob/main/android/app/build.gradle#L188
Happy coding! <3 |
yeah just to ensure everything is according to the setup instruction...btw, thanks! |
Can someone restate for me what was the fix here? It sounds like upgrading
|
In your example you're not using the same versions and also you're still using Android support (supportLibVersion) instead of AndroidX |
so how about the update ? how to fix this issue ? i'm facing this issue on RN 0.61.5 |
@pramahaditamaputra-ralali Using this solved the issue for me:
|
@naveenkirugulige hmm still not working for me :( |
@jdnichollsc did you found the best way to solve this issue ? |
Finally the issue has been solved, i changed the version number from this "react-native-inappbrowser-reborn": "^3.4.0" to this one "react-native-inappbrowser-reborn": "3.4.0" and its compatible with my current RN Version 0.61.5 ( removed this ^ symbol ) |
That's not true, this plugin supports old versions of RN, you need to learn more about Android 🙂 |
@jdnichollsc yup i know it maybe some of you have a better way to solve this issue, but in my case the new release version 3.6.1 give an error to my App built with React Native Version 0.65.1 and i try to downgrade it to 3.4.0 and its work ☺ |
Are you using Android Support or AndroidX? PD: You're going to need the fixes we have in the last version 🙂 |
The codebase of my project i handle it have some legacy code from RN Below 0.60, i tried to follow some suggestion such as update my Android Studio to the lastest stable version 4.2.2 and update the SDK and the gradle also, and then tried to only use the Android Support or Android X settings in the build.gradle file but it still same not fix my issue, the terminal always shows the error same as this post. And the error happened because the library get update to 3.6.1 version and works well in Version 3.4.0 ~ 3.5.1 |
|
You need to attach a repository to be able to reproduce your issue, I can't help you with the same logs 🙂 |
Hey @jdnichollsc , i'm facing the same problem. How could I solve this problem for Android support? Click here to see package.json
Click here to see build.gradle(project)
Click here to see build.gradle(app)
|
fyi: i'm trying to migrate my app to AndroidX... |
Good question, with Android Support I'm not sure if exist any option or conditional compilation flag to avoid this issue, let me check, any pull request is welcome in the meantime! ❤️ |
the error of this issue was gone but i get stuck in app run attempt:
|
okay, for those in the future: To solve the problem with
To solve the problem above with in build.gradle of the project add:
And in your
Hope it's helps you. |
More details here: https://stackoverflow.com/a/62785094/1532821 |
@jdnichollsc i wake up and decide to give a try to fix this issue for these projects in Android Support xD |
@mikehardy hello mate, hope you're doing well |
Hey there - not to put too fine a point on it, but no time at all should be spent attempting to make things work with Android Support Libraries. It's been 2 years since AndroidX was released and Android Support was deprecated, while I empathize with the difficulty of upgrading in some cases and I certainly sympathized (past tense) which is obvious since I created the jetifier tool to help everyone, I am out of present-tense sympathy for the situation. People need to update. |
Ok, the only option I found is using Reflection, e.g:
I'm going to create a new release with this solution <3 |
For people well and truly stuck there's always patch-package to hack in compatibility inside current versions or to hack in current fixes to old versions. I would spend no time on it vs investing the time in actually moving forward but if you're stuck you're stuck, so it's worth mentioning. |
@mikehardy thanks for your comments! I really appreciate your time and help! <3 |
@reberthkss what do you think? #281 |
It was fixed in v3.6.2! Thanks @reberthkss for your help! <3 |
Which platform(s) does your issue occur on?
Package.json
The text was updated successfully, but these errors were encountered: