-
Notifications
You must be signed in to change notification settings - Fork 468
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
Issue compiling android #128
Comments
Hi @phyzical , What version of RN you're trying to use? Do you have any other As you can see here, AsyncStorage is not relying on any deps, but RN. thanks. |
Hey thanks for the speedy Reply! i might here is the full npm list i know its a tad large... RN 59.9
i have been spending the last week bringing this app back to life haha, fixed it all and decided to get ride of the "last deprecation warning" >.> as for "if its another implementation" i dont think so.. ((but i could be wrong)) as syncing the gradle once the configs for the new Async implementation are removed fixed the android x warning |
@phyzical The issue here is that you're mixing Try using |
Hey, maybe i didnt make it clear,
Do i maybe need to use an older community-async version? not 1.5.0? |
Same issue suddenly appear while building android prod in RN 0.59.5. I have upgraded to 0.59.9 but the problem still persists. Downgraded lib to 1.4.1, Getting this on building
|
@chinmaygit i dont think our problems are connected maybe create a new issue |
Its very unpredictable and unstable working with RN. @phyzical i got the same error as you mentioned above, |
Hey @phyzical, This issue is about I believe you could try to migrate to You can both (@chinmaygit 👋) check out this issue here: the facebook/react-native#25293. Maybe the solution proposed will work for ya. |
Hey @krizzu, Thanks for the hand holding ;) your link sent me to here facebook/react-native#25292 (comment)
in my case device info was enforcing firebase:+ so pulling 19 and then triggering androidx thanks for the help im not sure why updating async caused this issue though haha.. i guess i updated device info and forgot? anyway clear to close if i can get my year old app with this many dependencies going on the release before androidx im sure must others can too GL to those i feel your pains |
@phyzical Happy to hear you solved it. :) |
I solved it by upgrading react-native packages without refactoring to androidx cause that action created cascades of issues to resolve =( |
This really helped me to solve the issue. Thanks Bro. |
@krizzu how can i come back com.android.support libs again.. |
I ran into this issue when i tried to use a fork of my own version of react-native. I was able to fix the issue by following this article: https://github.com/facebook/react-native/wiki/Building-from-source |
Cant build once adding the includes for async in android configs get the below warning before building
dependencies using groupId com.android.support and androidx.* can not be combined but found IdeMavenCoordinates{myGroupId='com.android.support', myArtifactId='drawerlayout', myVersion='28.0.0', myPacking='aar', myClassifier='null'} and IdeMavenCoordinates{myGroupId='androidx.core', myArtifactId='core', myVersion='1.0.0', myPacking='aar', myClassifier='null'}
and the following on attempting to build
Manifest merger failed : Attribute application@appComponentFactory value=(android.support.v4.app.CoreComponentFactory) from [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91 is also present at [androidx.core:core:1.0.0] AndroidManifest.xml:22:18-86 value=(androidx.core.app.CoreComponentFactory). Suggestion: add 'tools:replace="android:appComponentFactory"' to <application> element at AndroidManifest.xml:15:5-57:19 to override.
Expected behavior
compile
Environment
i understand it should be able to change androidx to fix the issue which i tried but i have too many dependencies that are not compatible i think.
Removing the references to async fixes the warnings and it compiles
am i forced to start deprecating these and replacing them with my own code or should i maybe rollback the integration of the new async implementation for now?
IOS builds fine
Thanks!
The text was updated successfully, but these errors were encountered: