I’m working on updating my app to Meteor 3.0rc0. I’m seeing this a lot, on the client, and also on the server in my GraphQL resolvers: Meteor.userId can only be invoked in method calls or publications. For example, in a GraphQL resolver on the server, this line throws: const userData = Meteor…

Ok maybe it’s something 3.0 related then I haven’t migrated yet :slight_smile:

Thanks for reporting this. I’ll try to simulate it and see what’s happening.

Here’s a small demo app. Incorporates minor updates to Meteor Apollo Skeleton for Meteor 3 Does not require Meteor package swydo:apollo Demonstrates that Meteor.user() cannot yet be accessed in resolvers [image] GitHub - VikR1000/apollo-skeleton-suggested-minor-updates Contribute to V…

I’m actually running into this right now. Did a proper fix ever get posted? I get null for both Meteor.userId() and Meteor.user() on the client side.

When are you using these values Are you certain that the user has already logged in by the moment you are using them? Open the console of your browser and execute Meteor.user() while running the app. What did you get?

I’m trying to add the newly registered user to a role, and thus the user Id is useful for that. I believe they are logged in after the initial creation, but may need to put some logic to make sure they are logged in already. When I am logged in and have the app running, I can see the Meteor.…

It was #2 for sure. I was calling the Meteor.user() too soon, and the user wasn’t fully logged in yet. Still getting used to this whoel async / await stuff. Now I await the account creation, then it gives me the user object. Thank you.

Also potentially helpful: const isLoggingIn = Meteor.loggingIn();

[image] bmcgonag1: I’m trying to add the newly registered user to a role, and thus the user Id is useful for that. Check the documentation about Accounts.onCreateUser(), which should be the ideal place to add default roles to a new account. Erratum: I only realized now that I was talking ab…

@vikr00001 yes, you can use userId and user only in methods and publications. If you want to use it in your Appollo or somewhere else, for example Meteor Cron, you cannot use Meteor.userAsync() or Meteor.userId(); In this case, you need to get user “manually”. This is the most simple way: Get user…

Meteor 3 - "Meteor.userId can only be invoked in method calls or publications."?

help

vikr00001 April 14, 2025, 1:24pm 16

It may not be secure to get Meteor.userId() on the client and send it to the server. Here is server-side code to get Meteor.userId():

Note the post right after that one as well.