Mention the --generatemissingstoragekeys option in README and help (ref.: #352)

Author: bepaald

README.md

@@ -688,7 +688,7 @@ Make sure your Signal-Desktop instance is cleanly shut down before running, if t
 
 To limit the message import to a certain time frame, the option `--limittodates <LIST OF DATES>` can be added. The format of the list of dates is identical to that of the [croptodates function](#crop-to-dates). In most cases, the option `--autolimitdates` can be used to automatically only import messages from the Desktop database before the first, or after the last message in the input backup.
 
-This function has some limitations to what gets imported, for example, some status messages are likely to be skipped (see [here](https://github.com/bepaald/signalbackup-tools/issues/57#issuecomment-1329475240)). By default, messages sent by/to contacts not present in the input Android backup file will be skipped as well. To prevent this, either make sure the contacts are present in the Android backup, or add the `--importdesktopcontacts` option. As of writing (2025-03-22), this option is still fairly new, but has been tested successfully a number of times. Details can be found in [this issuecomment](https://github.com/bepaald/signalbackup-tools/issues/250#issuecomment-2414052506) (and the rest of that issue thread). It may be necessary to disallow Signal access to your contacts when creating the initial backup file when using this option ([ref](https://github.com/bepaald/signalbackup-tools/issues/250#issuecomment-2858673661)).
+This function has some limitations to what gets imported, for example, some status messages are likely to be skipped (see [here](https://github.com/bepaald/signalbackup-tools/issues/57#issuecomment-1329475240)). By default, messages sent by/to contacts not present in the input Android backup file will be skipped as well. To prevent this, either make sure the contacts are present in the Android backup, or add the `--importdesktopcontacts` option. In some rare cases, certain group-recipients can not be created even with this option. If you are running into this, please see [this issuecomment](https://github.com/bepaald/signalbackup-tools/issues/352#issuecomment-3651563963) for possible workarounds (and the rest of the thread for details). As of writing (2025-03-22), this option is still fairly new, but has been tested successfully a number of times. Details can be found in [this issuecomment](https://github.com/bepaald/signalbackup-tools/issues/250#issuecomment-2414052506) (and the rest of that issue thread). It may be necessary to disallow Signal access to your contacts when creating the initial backup file when using this option ([ref](https://github.com/bepaald/signalbackup-tools/issues/250#issuecomment-2858673661)).
 
 **<span id="json">Importing conversations from JSON file / Telegram</span>**
 

arg/usage.cc

@@ -220,6 +220,9 @@ R"*(
    --desktopkey <HEXKEY>                 Optional modifier for `--importfromdesktop` and `--dumpdesktopdb`.
                                          Provide the decrypted SQLCipher key for decrypting the desktop
                                          database (see README).
+   --generatemissingstoragekeys          Optional modifier for `--importfromdesktop`. Generate random
+                                         storageIds, if they are missing from the database. Please see
+                                         github issue #352 for details before using this option.
 --deleteattachments                      Delete attachments from backup file.
    --onlyinthreads <LIST_OF_THREADS>     Optional modifier for `--deleteattachments' and
                                          `--replaceattachments'. Only deal with attachments within these

autoversion.h

@@ -20,6 +20,6 @@
 #ifndef VERSION_H_
 #define VERSION_H_
 
-#define VERSIONDATE "20251207.184840"
+#define VERSIONDATE "20251214.170740"
 
 #endif