Strange, strange behavior on iOS. Meteor.call will not work while phone is in the background.

[pmwisdom]

I installed this plugin and all of the sudden all my background geolocation updates stopped occurring, which happen through a series of meteor calls. I uninstalled the plugin and just like that they started up again. No clue why that would be

[mbanting]

That's weird. Thanks for letting me know. Do you know if it has anything to do with the geolocation lookup? Or is it strictly an issue with Meteor.call not being invoked anymore while in the background?

[pmwisdom]

Geolocation was good. Geo Callback fired, but any Meteor.call in the callback was "put on hold" until I put the app back in the foreground and then they all spooled up and fired. Without the plugin they all occurred correctly.

So if I did:

function(location) { //Callback for location from bgGeo plugin
    console.log('Before Meteor.call')
    Meteor.call('ping')
    console.log('After Meteor.call')
}

It would log the outputs to the console while inspecting the device, and then when I would put the app back in the foreground all the meteor.call's that piled up would trigger and I would see a pong outputted on the server.

I'll test it out a little more when I have time.

[TechplexEngineer]

I had a very similar problem. But on Android. It seemed that nothing would happen when the app was in the background. I found that in the dependency "skinnygeek1010:[email protected]" there was a call to meteor.disconnect() this was the problem.

We pulled the package local and removed the dep and just pulled the addEventListener calls into the package removing the calls to meteor.disconnect() and meteor.reconnect().

Hope that helps