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

[Bug report]: "Chrysalis database migration failed" Error message #7543

Closed
2 tasks done
CrashOverride-lab opened this issue Oct 4, 2023 · 5 comments
Closed
2 tasks done
Labels
bug report Something isn't working as intended

Comments

@CrashOverride-lab
Copy link

Platform

Desktop

Version

2.0.1

Description

After Upgrading from 1.7.5 to 2.0.1 when i try to open a Profile it says:

Wed, 04 Oct 2023 16:36:36 GMT
wallet: Chrysalis database migration failed: migration failed CipherError { alg: "XCHACHA20-POLY1305" }

I recovered for a test my old Ledger Firefly Folder from an old Backup. Uninstalled Firefly 2.0.1 and installed Firefly 1.7.5 --> Profile works like a charm. Upgrading it again to 2.0.1 --> Same Error see above.

In my Firefly are two profiles --> one based on Ledger and one from Stronghold. --> No one is accessible and after PIN-Entry the Error appears on both Profiles.

Expected behaviour

A Clean Migration including all Transactions where in the Profile.

Actual behaviour

See description

Can the issue reliably be reproduced?

Yes

Steps to reproduce the issue

See Description

Operating System

Windows

Diagnostics

App Name: Firefly
Version 2.0.1
Sprache: de
Plattform: win32
Plattformversion: 10.0.22621
Plattform-Architektur: x64
CPU-Anzahl: 24
Gesamtspeicher: 32488.7 MB
Freier Speicher: 17552.8 MB

Developer Profile

No

Profile Type

Hardware (Ledger)

Staking

None

Crash Status

None of the above

Error Messages

wallet: Chrysalis database migration failed: migration failed CipherError { alg: "XCHACHA20-POLY1305" }

Error Logs

wallet: Chrysalis database migration failed: migration failed CipherError { alg: "XCHACHA20-POLY1305" }

Duplicate declaration

  • I have searched the issues tracker this issue and there is none

Code of Conduct

  • I agree to follow this project's Code of Conduct
@CrashOverride-lab CrashOverride-lab added the bug report Something isn't working as intended label Oct 4, 2023
@begonaalvarezd
Copy link
Member

We are working on a fix 🙏🏼

@marc2332
Copy link
Collaborator

Hey @CrashOverride-lab we have released a new version 2.0.2, can you give it a try and let us know if this is fixed for you? 😄

Thank you!

@CrashOverride-lab
Copy link
Author

Hi Marc,

unfortunatelly Version 2.0.2 only helps with the Problem on Stronghold Profile.

The Ledger Profile displays now:

image

But i was in Contact with Thoralf about this and he means, that in the Next Release this should be fixed. Can you estimate when the next Version will be available?

@begonaalvarezd
Copy link
Member

Hi Marc,

unfortunatelly Version 2.0.2 only helps with the Problem on Stronghold Profile.

The Ledger Profile displays now:

image

But i was in Contact with Thoralf about this and he means, that in the Next Release this should be fixed. Can you estimate when the next Version will be available?

We found and fixed the issue you describe in this message too, we will release a new version as soon as possible

@begonaalvarezd
Copy link
Member

Fixed by #7600 & #7572, we will release a new production version very soon

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

No branches or pull requests

3 participants