Skip to content
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

"The user must update to continue" on most recent version (Linux) #200

Closed
tylerdq opened this issue Dec 5, 2023 · 4 comments · Fixed by #201
Closed

"The user must update to continue" on most recent version (Linux) #200

tylerdq opened this issue Dec 5, 2023 · 4 comments · Fixed by #201
Assignees
Labels
bug Something isn't working

Comments

@tylerdq
Copy link

tylerdq commented Dec 5, 2023

Describe the bug
Program does not successfully interact with my account, throwing the following error:

error: Server responded an error : {"requestId":"<ID>","errors":[{"type":"business_error","code":"expired_version","message":"This version is no longer supported. The user must update to continue."}]}

Please note that I removed the requestId in case it is a secret but I can provide it if needed.

To Reproduce
Steps to reproduce the behavior:

  1. run dcli p
  2. Run dcli sync
  3. See errors

Expected behavior
I expected the commands to retrieve a password and to sync without error.

Environment (please complete the following information):

  • Void Linux x86_64; Kernel 6.5.12_1
  • dashlane-cli version 1.15.0

Additional context
The same issue occurs whether I build with yarn or use the most recent released linux binary. This is strange because I'm running the same version (1.15.0) on another machine with Void Linux (though on kernel 6.5.13_1) and I am able to sync just fine on that machine. I have previously been able to sync on the machine that's experiencing this bug.

@tylerdq tylerdq added the bug Something isn't working label Dec 5, 2023
@Mikescops
Copy link
Member

Hello,

Sorry for this, a new rule on the server side has blocked the CLI, thanks for reporting, we're fixing it asap.

@Mikescops
Copy link
Member

Please note that I removed the requestId in case it is a secret but I can provide it if needed.

It's not a secret information and very valuable for any debugging in our side.

In that specific case no worries we don't need it 👍

@Mikescops
Copy link
Member

It's fixed in v1.15.1, thanks again for your report.

@tylerdq
Copy link
Author

tylerdq commented Dec 6, 2023

You're welcome! I built the new version with yarn and I am able to sync and retrieve passwords again. Thanks so much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants