Skip to content
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

[Android] Release mode is calling for .bundle instead of .jsbundle #42

Open
joaom182 opened this issue Jul 28, 2018 · 4 comments
Open

Comments

@joaom182
Copy link
Contributor

Crash java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Unable to load script from assets 'threads/pre-load-data-worker.thread.bundle'. Make sure your bundle is packaged correctly or you're running a packager server.

screen shot 2018-07-28 at 11 29 18

@Traviskn Traviskn added the bug label Aug 23, 2018
@Traviskn
Copy link
Contributor

Traviskn commented Aug 23, 2018

You're right!

The issue is here:
https://github.com/joltup/react-native-threads/blob/master/android/src/main/java/com/reactlibrary/RNThreadModule.java#L182

We need up update the code to look for a .jsbundle suffix rather than a .bundle suffix

@spidergears
Copy link

@Traviskn I was planing on using background threads and sharing them across multiple screens/activities, this seems like good project being inspired from the earlier two which are no longer maintained.

Coning to the issue, is changing .bundle to .jsbundle only change needed for this to work?
If that is the case I would be haapy to raise a PR, otherwise too let me know how can I help here.

@Traviskn
Copy link
Contributor

yep that's the only change. I found that in our app we're just generating a .bundle file for android and a .jsbundle for iOS, but it would definitely be nice to make that more consistent

@saalihou
Copy link

saalihou commented Dec 24, 2019

This and the fact that the README states that the bundle should be generated with a .jsbundle is probably confusing a lot of newcomers who wouldn't have the reflex to look at the logcat. Is there a reason it is still not fixed (backwards compatibility ?) or is it just noone did a PR.

If it is just a PR, I can make one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants