Stuck on login

[Nils Achermann]

im stuck on the floing i enter an email wich is valide i can lpogin to the website etc but still get 

C:\Users\nilsa>acli rovodev auth login
✗ Error: email is not valid, please provide a valid email address

C:\Users\nilsa>

[ashu patel]

CLI Email Not Valid

• Use the Command Prompt, not PowerShell, to run the login command—PowerShell often causes issues with special characters like @ in emails.

• Enter your email using the --email flag for best results:

  text

  acli rovodev auth login --email "your@email.com"

• Double-check for typos, spaces, or quote issues in your email address.

• If it still fails, check if your workspace has Rovo Dev agents enabled and review the CLI logs for more error details.

This is usually fixed by switching to Command Prompt and making sure your email is entered correctly.

[ashu patel]

If you’re getting the error Error: email is not valid, please provide a valid email address when running:

acli rovodev auth login

even though your email works on the website, here’s what to check and how to solve it:

1. Check How You’re Entering the Email

• The Rovo Dev CLI sometimes has trouble with special characters (particularly @) in the email field when run from Windows PowerShell. This is a known issue.

• Try running the command in the standard Command Prompt (cmd.exe) instead of PowerShell, and carefully type or copy-paste your email.

2. Use the Correct Command and Options

• The recommended way to provide your email is with the --email (or -e) flag:

  acli rovodev auth login --email "your@email.com"

• For the API token, either enter it interactively, or save your token to a file (e.g., token.txt) and run:

  acli rovodev auth login --email "your@email.com" --token < token.txt

• Double-check for extra spaces, quotation issues, or typos in your email.

3. Known CLI Issues

• Some users report not being able to enter the “@” character in email on some Windows setups. In these cases:

  • Solution: Run the CLI via Command Prompt (not PowerShell) or paste the email instead of typing.

  • You can also try running the command with all arguments specified at once (vs. interactively).

4. If You Still Get the Error

• Make sure your site/workspace has Rovo Dev agents enabled—if not, authentication may fail with strange errors.

• Check the CLI logs at:
  C:\Users$$yourname]\.rovodev\rovodev.log
  for more details on the exact validation problem.

• If none of these steps work, report the bug with your log to Atlassian.