-
Notifications
You must be signed in to change notification settings - Fork 26
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
Module breaks Android build: Detected multiple Kotlin daemon sessions at build/kotlin/sessions & other errors #8
Comments
Hey Lennart! Looks like a version mismatch, see the compatibility table in the README:
Can you try to pin to a lower version and see if you still get the error? If you do, I'll take a closer look. |
Hi Jonny, oh yes, sorry for that! I just installed "react-native-animateable-text": "0.5.9" and now, the App just crashes on launch. Just to make sure, I then removed the module and it didn't crash without having react-native-animateable-text in my project.
|
Nevermind. I just tried to find out why it crashes with adb logcat and suddenly the App starts again. Thanks a lot for helping me out! I hope this issue helps the next developer who's stuck with version missmatch :D |
Ok, that's great to hear! 😊 We are running the same version. And although we get the same warning, it doesn't lead to a crash. I think I can remove the kotlin plugin, I'll try and remove it in the next version (I know you need to run an old version but hopefully you'll upgrade too when RN64 is officially out). |
I actually removed the kotlin plugin and then the App crashed 😅 So I just ignored the warning. |
Hi there,
I'm glad I found your package as it's exactly what I am looking for. But after installing the module, my Android build stops working. Here's the console output:
I'm using the following module versions:
Is there anything else you need to know?
UPDATE:
Commenting out the apply plugin 'kotlin-android' in the module's build.gradle and then running yarn again seems to resolve the first part of the error message. The build still fails because of the 3 other error messages.
The text was updated successfully, but these errors were encountered: