You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When logging in with custom credentials I am able to run clasp pull/push/run successfully.
Actual Behavior
When attempting to log in with custom credentials I receive:
Authorization successful.
Local credentials saved to: ./.clasprc.json. Be sure to never commit this file! It's basically a password.
Could not read API credentials. Are you logged in globally?
The .clasprc.json file is created and contains what looks to be the correct content.
Expected Behavior
When logging in with custom credentials I am able to run clasp pull/push/run successfully.
Actual Behavior
When attempting to log in with custom credentials I receive:
The
.clasprc.json
file is created and contains what looks to be the correct content.Steps to Reproduce the Problem
{ "installed": { "client_id": "asdf.apps.googleusercontent.com", "project_id": "asdf", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "token_uri": "https://oauth2.googleapis.com/token", "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs", "client_secret": "asdf", "redirect_uris": ["urn:ietf:wg:oauth:2.0:oob", "http://localhost"] } }
clasp login --status
returns:Please note that the regular method of logging in (
clasp login
) is successful.Debugging shows that
dotfile_1.DOTFILE.RC = {exists: ,read: ,write: ,delete: }
Specifications
node -v
): v12.10.0clasp -v
): 2.3.0The text was updated successfully, but these errors were encountered: