-
Notifications
You must be signed in to change notification settings - Fork 87
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
Library fails with "this.auth.getUniverseDomain is not a function" #1557
Comments
Issue originates from #1552 which added the dependency to the newer version of google-auth-library. And to clarify, people will want to verify that their package-lock.json does not have |
Hi @Rochet2, if you delete your package-lock.json and reinstall dependencies, you should pull in the latest version of the auth library. |
I can do that, but it is not necessarily viable long term fix and does not address the larger problem. I am not the only one that will run into the issue. Doesn't gax have a way to control its own dependencies so they would work with the library? |
Looks like this is the correct place to edit Line 18 in d9bbb8c
|
I'm still seeing this issue using the following: @google-cloud/[email protected] I've skimmed my package-lock.json to confirm no sub dependencies are pulling in old library versions. |
I keep on having this issue as well 😢 |
Is this a client library issue or a product issue?
It is a client library dependency issue. Gax depends on features that exist on newer version than what is installed.
Did someone already solve this?
Did not find any issues by searching with
getUniverseDomain
.Please create an issue in the support console to ensure a timely response.
If the support paths suggested above still do not result in a resolution, please provide the following details.
Environment details
Steps to reproduce
"@google-cloud/pubsub": "4.3.0"
this.auth.getUniverseDomain is not a function
"google-auth-library": "^9.0.0"
, butgetUniverseDomain
was introduced in v9.3.0 here. We havegoogle-auth-library: "9.0.0"
installed.The text was updated successfully, but these errors were encountered: