-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accounts.onEmailVerificationLink throws console warning when being used #11116
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is ignored not stale |
@dcantatore Can you share with us list of packages you are using? Just to cover all our bases. |
|
Hi, could you provide a reproduction? 😉 Read more here |
Hi @filipenevola , It's really simple, create a new meteor project and add:
It can be put in any top level code 'This function should be called in top-level code, not inside Meteor.startup().' as stated here: |
Could be related to this reported problem/bug : [1.8.3] onLogin handler fired twice #10853 The above onLogin handler fired twice bug was reported to be related to this code change & commit: Simplify _startupCallback by passing callback rather than ID. (ec0ed4d) Which was introduced in this PR #10543 which was resolving this bug/issue: #10157 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed it has not had recent activity. |
I also have this issue. I understand there may not be an easy way to reproduce this, but thought I'd chime in for the record. |
When you use Accounts.onEmailVerificationLink() on the client side as instructed, in the console it says:
The meteor doc around it is:
https://docs.meteor.com/api/passwords.html#Accounts-onEmailVerificationLink
It says "This function should be called in top-level code". Which it is, so I'm not sure where else I would put it to avoid this bug
I have seen this mentioned as a feature request but this is a bug
The text was updated successfully, but these errors were encountered: