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

[Electron] Chrome backup import error #1531

Closed
1 task done
mmirg opened this issue Oct 3, 2017 · 3 comments
Closed
1 task done

[Electron] Chrome backup import error #1531

mmirg opened this issue Oct 3, 2017 · 3 comments

Comments

@mmirg
Copy link

mmirg commented Oct 3, 2017

  • I have searched open and closed issues for duplicates

Bug description

I have installed the Electron desktop application on Linux but cannot import the backup from the Chrome app. I have tried both with the binary package provided by OWS as well as installing the code using npm and yarn. The Electron application appears to work fine if I delete the configuration information in ~/.config/Signal and set it up as a new application.

Steps to reproduce

  • Export data from Chrome application
  • Install Electron application
  • Attempt to import Chrome application backup

Actual result: The Electron application states that : "Unfortunately, something went wrong during the import. First, double-check your target directory. It should start with 'Signal Export.' Next, try with a new export of your data from the Chrome App. If that still fails, please submit a debug log so we can help you get migrated!"

Expected result: That the Electron app properly imports the message database from the Chrome application. Is there a way to temporarily re-enable the Chrome application while I attempt to resolve this?

Screenshots

Platform info

Operating System: GNU/Linux 4.13.4
Browser: 61.0.3163.100 (Developer Build) (64-bit)

Signal version: 0.43.4 / 1.0.27

Link to debug log

https://gist.github.com/5535651e34f421a0071c44175eef1bfd

@scottnonnenberg
Copy link
Contributor

Yep, you can reset the state of your Chrome App with these statements in the console:

window.storage.put('migrationState', 0);
window.storage.put('migrationEverCompleted', false);

Then after a little bit, restart with this:

window.location.reload();

@myf
Copy link

myf commented Oct 25, 2017

how do we trigger the migration-screen to appear? I have seen it in code but never get to see it. is this a hidden feature?

@myf
Copy link

myf commented Oct 25, 2017

well not sure if I did the proper thing, but just incase if anyone else has the same problem as I do, i did

Whisper.Migration.init()

followed by

window.location.reload()

which worked at the end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants