accessControl session var goes out of scope? maybe?

[lefnire]

accessControl session var goes out of scope? maybe?

[lefnire]

racer, derby, racer-db-mongo 0.3.12

[lackac]

This has happened in my app as well. I couldn't find the root cause but my experience is the same. I ended up checking in access control guards whether this.session is defined.

[lefnire]

good thinking, i'll play with that

[lefnire]

thanks @lackac , it seems checks on is defined have no side-effects (thought accessControl might go awry since this is a workaround, but I think we're good). I'll close for now an re-open if issues crop up.

[lackac]

This has bitten me eventually. I don't know why exactly, but when I try to access my application from mobile chrome (android or iPad) it keeps reconnecting. I finally found that the cause of it was this guard and the fact that this.session was undefined. What I don't know is why this doesn't happen on desktop, but does on mobile.

I kept debugging this going step by step into the depth of racer – interesting journey, btw. After a few hours of mind wrapping I got to the source of the problem. I have found that the only time this.session was undefined was when the client was making a snapshot request. The code segment linked above is the one which builds the req object in this case and that is the object from where this.session should be coming from. You can see that the session property is missing from the object.

I tried adding it to it and that did solve the issue for me. I have issued a pull request with that change.

[lefnire]

awesome. I'll test your patch soon & chime in.

[mjohnson9]

Any news on this?

[lefnire]

no updates on my part. i haven't yet tried removing @lackac's workaround because it works just fine with it in place. should i just close this ticket?

[lefnire]

@lackac's fix #40 indeed solved the problem. I've been running HabitRPG for a while now, using a the return unless @session and @session.userId workaround suggested above without problems. But for one reason or another, once you have multiple subscriptions on a page it breaks down - @lackac's fix solves this. Would that codeparty pulled requests :(

[nateps]

No longer relevant in 0.5