-
Notifications
You must be signed in to change notification settings - Fork 89
Documentation for running in release/production? #7
Comments
So, my Objective-C skills are nonexistent, but it seems to work if I hardcode the path to the worker bundle: Steps to get it working:
|
Having the same issue in android
Listing the assets I can't see the workers asset
|
A possible way to overcome this is to create the workers manually
|
yes it is on the todo list. but basically it is just a matter of calling the RN packager and writing the worker bundle file at the correct location. |
When are you adding this please @devfd |
Ok. I have done this. Its working now. |
Anyone else seeing issues with RN 0.35? I have a For the android bundle I'm running:
(my app's name is Even though the |
I'm having the same issue. WorkerManager.m looks like this: NSURL *workerURL = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:name fallbackResource:nil]; How do I find out where I am supposed to write bundle for iOS? |
I tried running a production version (Scheme -> Build Configuration = Release), the main bundle loads and attempts to start the worker, but this just repeats in my logs:
I added the
worker.js
file to my project folder and can confirm it's being copied to the same folder. But it looks like the worker is trying to load the wrong file? The main.jsbundle file is the output of the react native packager, right?The text was updated successfully, but these errors were encountered: