Both authentication methods are defined although I only use credentials file

[jdanthinne]

Hi,

I'm getting a strange error when using this step. I'm only referencing a credentials file, but in the log I can see "Both authentication methods are defined" and the command fails.

Configs:
* firebase_token:
* service_credentials_file: /var/folders/71/rszmbrmd6tv4pg52z6ql_5c0000gn/T/GENERIC_FILE_STORAGE1683874599/xxxxx.json
* app_path: /Users/vagrant/deploy/xxxxxxxxe.ipall
* app: 1:xxxxxxxxxx
* release_notes:
* release_notes_length:
* release_notes_file:
* testers:
* groups: decathlon
* flags:
* is_debug: false
* upgrade_firebase_tools: false
App path ends with || . Manually fixing path: /Users/vagrant/deploy/xxxxxxxxxx.ipal|
Both authentication methods are defined: Firebase Token (via FIREBASE_TOKEN environment variable) and Service Credentials Field, one is enough.
-- Checking for existing firebase-tools on PATH...
Your machine has [email protected] installed.
If you would like to upgrade your install run: curl -sL firebase.tools | upgrade=true bash
Deploying build to Firebase
firebase appdistribution:distribute "/Users/vagrant/deploy/ConnectedLockerSample.ipa" --app
"1:xxxxxxxxx" -groups "xxxxxxxxx"
Authenticating with 'FIREBASE_TOKEN' is deprecated and will be removed in a future major version of
'firebase-tools'. Instead, use a service account key with *GOOGLE_APPLICATION_CREDENTIALS*: https://cloud.google.com/docs/authentication/getting-started
uploading binary...
Error: Failed to upload release. Authentication Error: Your credentials are no longer valid. Please run firebase login --reauth
For CI servers and headless environments, generate a new token with firebase login:ci