-
Notifications
You must be signed in to change notification settings - Fork 586
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] Add 64 bit support for Android #2221
Comments
Thanks for raising this, appreciated. |
@kneth i do not force to anyone but i think this should be priority. And version 0.59 is behind door. This version should be compatible with Realm which will be great, but again, it enabling support even for x86_64. Android platform is involving in RN very quick. But another great change for RN0.60 (probability is very high) is that it replaces very unfriendly import Xcode libs with Cocoapods. And it will be default for all new projects. Do you have any plan how to be complatible with RN in very close time when new RN version will be released? |
@radeno Thanks for giving us the executive summary of RN roadmap. Every RN version seems to break something, so it is hard to stay on top of it. We are currently refactoring our code base and upgrading the Android NDK. Once those two tasks are completed, we can begin to look forward. Adding 64 bit support for Android should be trivial. Better Cocoapods support sounds great. |
I would also add, that we are very appreciative of PR's :-) and encourage the community to help in any way possible. Even if that's not a PR, making issues with details of upcoming breaking changes is also helpful. |
Marking as blocked as we are waiting for React Native 0.59 before we can enable this: facebook/react-native#2814 (comment) |
@cmelchior 0.59-rc3 release is one day old. It is probably last RC before production or will be rc4 with some small fixes. If this commit facebook/react-native@f3e5cce will not be merged into 0.59 (i hope not, it is too big change for current state) then rc3 is quite solid stable without such big changes before release production. |
@cmelchior my mistake. It is already in 0.59. So all big changes with JSI/JNI for Android looks like done. |
In facebook/react-native@f3e5cce React Native is changing to clang and |
RN is already at 0.59. It's stable! |
Can we get more attention on this? |
realm is not support 0.59(RN) now |
I'm confused... |
I believe that RN 0.59 requires some changes that we haven't had time for yet. |
I think people are getting a bit off-topic here. The original issue was support for 64-bit, not RN 0.59. I realise they are very closely related, but at the same time, as @cmelchior stated in #2282:
|
@FunkyLambda I feel you, but one of the bigger new features of RN 0.59 is 64-bit support. |
@diegolmello 64bit arrived with RN 0.58, 0.59 brings new JSI and compiler. |
@radeno |
@diegolmello x86_64 is intel/amd processor. AMR7/8 is 99,9% all mobile devices. |
@PanRada @TheusBrz Ensure your Android app/build.gradle is only building for 32-bit architectures. React Native 0.58 is when 64-bit first landed. So comparing the diff between the generated app/build.gradle, ensure your's uses 0.57 values...
Ensure that |
@BrandonSmith become able to run my app on Android but it breaks other functionalities and break my iOS app... I'm very excited to use RealmDB but I'm feeling that is not the moment... I'm not an excellent developer yet and my projects deliver dates are close... I plan to move to SQLite for now.. |
Any updates on this? Removing "x86_64" from gradle build files is not working. Edit. Looks like I had to also add: This looks really bad, forcing 32 bits just because a library. What would be the side effects of this? Edit 2: Using the above although allowed the app to run, it is now raising errors related to touch events that never happened before. I guess I will be staying away from Realm as well. Shame since it seemed very good when testing on other devices. |
Thank you for relaying your concerns. While I understand that this is an issue many care about, flooding the comments with "+1", "I want this fixed now!!11", etc. is not productive. When we have more information to share, we are going to update the issue. |
@nirinchev I'm anxious to start using Realm, I'll keep an eye on this issue to get news. I wish you a good coding :) |
Hey @nirinchev, I think people wanna know if this will be resolved before the deadline of 1st of August 2019 or not? |
It will |
Does anybody have a hot fix for arm64bit? |
It's being worked on now here: #2366. |
@trungthanhnt You need to combine #2221 (comment) and #2221 (comment) until we support 64 bit. |
this is fixed in v2.28.0 |
Nice work, @nhachicha @kneth! 👏👏👏 |
Thank you very much to fix this! |
We hear about crashes - most likely due to facebook/react-native#24261 - on Samsung devices. |
Has there been a decision on which version of |
@a-koka I don't think the React Native developers have a fix ready yet. |
anyway to support 64bit architecture in 0.55.4? |
@deepakverma4 You will need RN v0.59 (https://facebook.github.io/react-native/blog/2019/03/12/releasing-react-native-059) |
still crash on v3.5.0 RN v0.61.5 |
@0x01001 Please create a new issue - and remember to add all relevant information (outlines in the issue template). |
From August 1, 2019 Google Play will not accept apps with 32 bit only
.so
files. Currently, we only compile our React Native (Android).so
for ARMv7 and x86, but we should in good time provide 64 bit.so
files too.React Native (Android) added support for ARM64-v8a and x86-64 recently: facebook/react-native#18754.
Reference: https://android-developers.googleblog.com/2019/01/get-your-apps-ready-for-64-bit.html
The text was updated successfully, but these errors were encountered: