search

johanw666 / Signal-Android

Fork from a private messenger for Android with extra options added: full backup and (partial, ony text) xml backup of messages. Restore can happen at any time, not only after a fresh install. Import SMS database. Import of (unencrypted) WhatsApp databases. Removed apk expire. Choose between passphrase protection and the Android screenlock. Choice for the backup location (internal or removable storage on Android < 11 (on 11 and higher this is already possible)). Set the maptype in the place picker. Option to treat view-once media as normal media. Option to ignore remote deletion. Choose between FCM or websocket notification delivery.
https://johanw.home.xs4all.nl/Signal/signal-jw.html
GNU Affero General Public License v3.0
246 stars 16 forks source link

Importing WhatsApp messages fails #63

Open panomitrius opened 1 year ago

panomitrius commented 1 year ago

I just downloaded the lastest version of your Signal fork (6.0.1.0-JW) here on github, and trying to import a decrypted msgstore.db according to this guide fails. The Signal app just instantly says "Import complete", but nothing happens. I've tried putting in root directory and in root directory on the sd-card, doesn't help.. I'm running LineageOS with MicroG 19.1 on a Samsung phone.

Any idea what the issue could be?

johanw666 commented 1 year ago

Without a logfile, no idea. The WA database should be placed in the root of the "internal sd card", usually something like /storage/emulated/0 in absolute path. The documentation is somewhat unclear about this, I should improve that.

If you are a member of any groups in WA you shoudl create grouos in Signal with the same name before importing.

panomitrius commented 1 year ago

It is already placed in /storage/emulated/0 (I tried to remove it and then i get an error message, so I assume it's placed properly when I don't get the error message). I'm happy to share the logs, how do I access them?

panomitrius commented 1 year ago

Found a way to access the logs. The error message seems to be:

[org.thoughtcrime.securesms/org.thoughtcrime.securesms.ImportExportActivity#1] Invalid device requested composition type change: CLIENT (1) --> CLIENT (1)

There are more logs though, but it's quite massive only during a couple seconds, so instead of pasting more I'm attaching them here .

panomitrius commented 1 year ago

Any thoughts on this @johanw666..?

panomitrius commented 1 year ago

Found the prefered way to create a log, here it is: https://debuglogs.org/android/6.3.2/d58417710e26c852ef543fd8a47d3c37f4cd230f60d0612b7b09fefc6d45bc6b

panomitrius commented 1 year ago

I think the relevant info is:

[6.3.2.0-JW] [21457] 2022-11-22 18:51:48.827 GMT+01:00 W PlaintextBackupImporter: importWhatsapp(): importGroup: true, avoidDuplicates: false
[6.3.2.0-JW] [21457] 2022-11-22 18:51:48.897 GMT+01:00 W PlaintextBackupImporter: no such table: messages (code 1 SQLITE_ERROR): , while compiling: SELECT COUNT(*) FROM messages
[6.3.2.0-JW] [21457] 2022-11-22 18:51:48.899 GMT+01:00 W WhatsappBackup: no such table: messages (code 1 SQLITE_ERROR): , while compiling: SELECT * FROM messages LIMIT 0, 1
[6.3.2.0-JW] [21457] 2022-11-22 18:51:48.899 GMT+01:00 W PlaintextBackupImporter: Exited loop

I decrypted the msgstore.db.crypt15 file with ElDavoo/WhatsApp-Crypt14-Crypt15-Decrypter without any error messages.