Koen [XII]

I'm now thinking it may have to do with us not providing a requestCode, because of which 1 is used by default, but it seems requestCode is like an 'Intent...

@theodorDiaconu for us the problem exists because we apply a Tenant scope to (most of) our Collections, which relies on Meteor.userId(). The following part of the code is not executed...

Relates to: https://github.com/cult-of-coders/redis-oplog/issues/369

I should mention I'm troubleshooting a Chrome App, but it has access to IndexedDB and localForage works fine, so it shouldn't be an issue. I'm subscribing to collections in Meteor.startup:...

1.2.1

"Again the GroundDB II does not cache/resume outstanding method calls or try to be clever about things" Does this mean it will no longer forward collection changes made when the...

I understand. I did however run some tests and it does seem that changes made to collections while the client is offline are later reflected on other clients after the...

I see, I was just a little worried that simple changes to a collection would not be 'resumed' after reconnecting with the server (e.g. it could leave clients out of...

The alpha seems to work fine here. Collections are available offline and outstanding changes are sent to the server when the connection is re-established. Changes made on other clients during...

@Ajaay thanks for the tip! Would that be windowSettings at the root of settings.json? Because the only windowSettings I see in our settings.json are within the splashscreen plugin.