Rovo Dev - Auth not working in Termux

[Jack 2023]

Rovo Dev don't work in my Termux:

I try to use the auth login:

'acli rovodev auth login'

and enter the email and token but get '✗ Error: authentication failed' 

I even try 'echo 'APITOKEN' | acli rovodev auth login --email 'EMAIL' --token' and replace the values but it don't work.

I double-check my email and regenerate a token and try but it don't work.

Thanks for replying!

[Leo Chiang]

Hi Jack 
Have you allow your email into group ?

You should allow into “rovo-dev-agent-user-YOURNAME” before your login .

• Go go https://admin.atlassian.com
• Directory > Users > Invite users
• Set user email
• Set Product Rovo Dev Agnets Roles  ”User”
• Or add Users into group “rovo-dev-agent-user-YOURNAME”
  
  

Can try try . ^_^

[Jack 2023]

I am trying, Leo Chang. :)

[Jack 2023]

I do everything but it don't work :(

[Leo Chiang]

Do you have 2 or more site ? It's will only allow in your main site so far .

[Jack 2023]

I have only 1 site

[Leo Chiang]

Hi Jack . i can offline help you on this issue if you want . please contact with me the email.

leo.chiang@titansoft.com.sg

[Victor Feight]

I get the exact same issue on Windows WSL and I do not believe it is tied to any configuration or API key issue; I think this is a service-side issue on Rovodev's part. Started happening for other users here too, not just us: https://community.atlassian.com/forums/Rovo-questions/acli-rovodev-auth-login-says-success-but-API-calls-still/qaq-p/3058955

Convenient timing too, since it's just days before our 20m daily are about to expire, lol. I'm pretty sure there is no way to fix this, deleting config and logging out logging in doesn't work, looks like something that should be addressed at scale not in a forum.

[Jovana Dunisijevic]

Hey @Leo Chiang thank you so much for helping out @Jack 2023 !

Have you been able to resolve the issue?

[Jovana Dunisijevic]

Hey @Victor Feight 

Thank you for sharing these details and for linking to the other community thread. We’re aware that several users are experiencing the same issue.

Based on what you and others have reported, this does appear to be a service-side issue with Rovo Dev, not something you can resolve locally. The timing and the fact that it’s affecting multiple users suggest it’s not related to your configuration, API key, or environment.

What you can do:

• Please check the log file at ~/.rovodev/rovodev.log for any additional error details. If you’re comfortable, sharing relevant log snippets (with sensitive info removed) can help the team investigate.

• Since this is likely a backend/service issue, the best next step is to report it directly to Atlassian via https://support.atlassian.com/rovo/docs/troubleshoot-problems-with-rovo-dev-cli/ and https://support.atlassian.com/rovo/docs/troubleshoot-problems-with-rovo-dev-cli/ . Include your log file and a description of what you’ve tried so far.

This is being tracked as a known issue during the beta, and it will need to be addressed at scale by the Rovo Dev team. Thank you for your patience and for helping us improve the product.

Kindest regards,
Jovana