-
Notifications
You must be signed in to change notification settings - Fork 140
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
Any guidance on using this library with version 0.70? #155
Comments
@ThalesBMC the problem is that facebook removed some of the java class files that were previously included in react native, the only way to fix this is a complete rewrite, Ive run into the same problem with my library which was a fork of this one, https://github.com/austinksmith/react-native-hamsters I managed to fix some of the issues with this react-native-threads library but supporting versions higher than 0.6.9 seems to be very difficult |
@austinksmith any updates perhaps? I'm working on a new app, so I have some flexibility with versioning and that, but I've really battled to find an up-to-date way to run processor-heavy async tasks away from the main thread (a TFLite model in my case). Would appreciate any help you can offer! |
@devsticks I would recommend using my library Hamsters.js ( https://www.hamsters.io ) and using my react-native-hamsters package, as long as you use react native 0.69 or older it will work and you can follow my api and do some really cool stuff like put a function on its own thread or split a for loop across multiple threads just by changing 1 parameter. Eventually I'll try to tackle support for version 0.70 and newer but I took a look at the latest reactnative and they've completely removed ALL of the java files that this package and my package rely on so its going to take sometime to figure it all out. In the meantime you can use hamsters.js with react-native-hamsters and do parallel processing / multithreading without having to worry about things like thread communication and stuff. |
We need something like Did you, by any chance, had the time to look a bit into it? We're willing to pledge a 2k$ bounty to solve this issue in the open-source ecosystem, if that helps. That said, we're on tight schedule, and cant wait very long or else we'll have to do it ourselves (by "long", I mean that we'll start investigating around february). We just think it would be a shame to do that closed-source. Would it be something that is interesting to you ? (or anyone reading this, for that matter) |
@oguimbal While I'd love to help this is a big undertaking, facebook stripped out all the java files that these libraries both rely on. Without this java functionality we can't make it work, and recreating all the functionality of the old java files that used to be bundled with react native would be a major amount of work. I might be able to provide support for 0.70 but i couldn't do anything newer than that. |
Hi @oguimbal, I've come across the bounty offer for addressing the multi-threading issue in React Native >0.70 with Expo, and I'm interested in contributing to a solution. With the sponsorship you've proposed, I believe I can offer valuable assistance in this endeavor. If you're still looking for support on this project, please feel free to reach out to me at [email protected] so we can discuss the details further. |
Hi @oguimbal PR: #156 |
Hi @gaodeng i am using your forked library for a non-expo project. I ended up on this error when the new architecture is enabled. Whenever i comment the line in MainApplication.java
The error i mentioned in the github issue goes away. Can you help me or guide me to resolve the issue? project info
Error log
|
Is this for expo only? It doesn't seem to patch support for the old java packages for react-native. When I took a look at this support for 0.70 was required recreating some logging package that was removed. |
The library no longer functions with version 0.70 of react native.
Any suggestions for resolving this issue or using an alternative library?
The text was updated successfully, but these errors were encountered: