Constructor with protected function does not provide this.userId in Meteor 3

[jmaratt]

Context no longer provides userId in Meteor 3. userAsync() also provides null.

[jmaratt]

Using:

Meteor 3.2.0

accounts-password 3.1.0
ostrio:files 3.0.0-rc.3

[dr-dimitru]

@jmaratt thank you checking this one

[jmaratt]

@dr-dimitru let me know if I can do anything else to help with this.

Do you know of a reasonable workaround to this issue until fixed? Thanks!

[manuel-schoebel]

Somehow it seems that ostrio files is expecting an mtok token either as a header or in a cookie. But in my request to the image, no sign of any mtok token.

[fmorgens]

I have the same issue with ostrio:files 3.0.0-rc.3 and METEOR@3.0.2 (no userId and null from userAsync())
However in my case the x-mtok cookie is set but Meteor.server.sessions seems to be empty

[fracz]

Same here. Confirms that the request contains the x_mtok cookie, but userId is null.

[mitsol]

Same here! Would be happy to have a workaround.

[jmaratt]

Anyone figure out a workaround? Thanks in advance!

[jankapunkt]

@dr-dimitru do you estimate this as an issue with the cookies package or with this one?

[gfbeqs]

For me it works with Meteor 3.3.1 and ostrio:files@3.0.0-rc.1 but not with ostrio:files@3.0.0-rc.2 or ostrio:files@3.0.0-rc.3

[bhunjadi]

For me it looks like the problem is in _getUserId function and the fact that Meteor.server.sessions is empty.

Meteor: 3.3.2
ostrio:files@3.0.0-rc.3

However, after restarting the app it started to work for whatever reason.
This was in development, i.e. I ran the app with meteor command.

Note that it appears I'm experiencing this with Meteor v2.16, too.

[dr-dimitru]

@jankapunkt just finished with testing. Yes it was related to cookies, going to push fix soon