Invalid State Error after bundling about react-native-meteor-boilerplate HOT 6 CLOSED

A few things:

• Try to use node-ddp-client instead (has a few fixes)
• Make sure you add your production server url here and change env to prod or staging.

from react-native-meteor-boilerplate.

just for information, everything works absolutely fine in simulator, it's when I bundle the app on the device that the websocket connection somehow is not working and shows the error.

So I tried to change to node-ddp-client: I still got the error page on the device, and in the simulator I can connect through the signin page, but none of subscriptions are working.

And I didn't add the production server url in Appdelegate.m because I commented it and uncommented jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"]; to get the offline bundle...

I also tried many different config for the ddp connection (socketConstructor, ddpVersion...).

from react-native-meteor-boilerplate.

The problem comes from my meteor server (1.3 with imports/ directory structure)... Strangely, I can establish a connection to it through the simulator but not on the device. I tried with a meteor server (1.2 with old directory structure) and it's working fine...

How is that possible?

from react-native-meteor-boilerplate.

I'm finding that 1.3 has caused many of my builds to fail; necessitating revising from scratch with the new directory structure.

Pain in the arse. Native with php is starting to look attractive again!!

Sent from my iPhone

On 1 May 2016, at 7:18 PM, Yohan Sihou [email protected] wrote:

The problem comes from my meteor server (1.3 with imports/ directory structure)... Strangely, I can establish a connection to it through the simulator but not on the device. I tried with a meteor server (1.2 with old directory structure) and it's working fine...

How is that possible?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

from react-native-meteor-boilerplate.

Ah, yeah you're right about the Appdelegate.m - no need to change that url in this instance.

That's really strange that this isn't working in 1.3 but is in 1.2... are you getting an errors on the server? Can you connect to your remote/production server from the simulator (when it isn't bundled)?

Also what does your project architecture look like? If you have your react native app in your Meteor app's project structure it may be causing the issues.

from react-native-meteor-boilerplate.

If there were any issues related to the boilerplate they should be fixed in the latest major update. Please let me know if not. Thanks!

from react-native-meteor-boilerplate.