Wire version: 3.10.3138
Wire for web version: 2019.07.11.1318
Operating system: Windows 10 Pro x64 1809 (Build 17763)
Which antivirus software do you have installed: Windows Defender
What steps will reproduce the problem?
(Original Problem/Bug: I was sending a timed message to somebody and lost my Internet connection, so the message was "stuck" and grey in color. When my Internet was restored, the message was still grey. I can only "Copy" the message, but the message doesn't delete. I thought "Let's take extreme measures and backup and restore from backup." Instead, that restored the stuck message.
I thought, "Ah ha! I have a Windows 7 Pro x64 machine with Wire. I will simply backup the Windows 7 Wire (without the stuck grey message) and restore on top of the Windows 10 machine to overwrite it."
Now I have duplicates of every message.)
What is the expected result?
I expect that any time I restore from backup that it overwrites the message history completely instead of duplicate.
What is the actual result?
Duplicates entire message history.
What is the safest way to proceed? On Android, there is "Perform full synchronization," but this is not available on Windows client.
I tried logging out and logging back in. Same.
I see many files stored in C:\Users\MyUserName\AppData\Roaming\Wire -- Is there something here I can delete to force delete the message history? I want to keep all my images and only delete the message history and then try to restore from backup again. Maybe C:\Users\MyUserName\AppData\Roaming\Wire\IndexedDB\https_app.wire.com_0.indexeddb.leveldb contents? I want to be extra sure before touching anything.
Hi @gopherit, that of course shouldn't happen, thanks for the report!
The easiest way to reset Wire is the following:
All your images which are not older than 6 months will be re-downloaded from the server (and decrypted) after switching to the appropriate conversation.
Thanks, deleting the Roaming\Wire directory was successful to force reset Wire Desktop, and I restored from the "good" backup from the other Windows machine, so nothing is duplicated now. The original issue is still a small bug, but thanks for the help in the workaround!