You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2019. It is now read-only.
the thread is a mix of other issues as well, not being able to create a backup in windows GUI or CLI when using --data-dir ... also 0.9.3 GUI did not use the data-dir when specified.
I was able at least to get a backup when using GUI with all data kept in default appdata directory but the wallet_export_keys does not create a json file on windows or linux.
Obviously this works for some people but not for me. I can only guess maybe it is to do with too many accounts or too many keys. (20 account, many with 30,000 or more generated keys) I've also always had issues with the transaction history never showing with this wallet, i presume due to some corrupted transaction memo. just guesses, i don't know what else could cause it.
The text was updated successfully, but these errors were encountered:
I've tried on windows7 x64 and linux ubuntu 14.04 both fail to create json file.
https://bitsharestalk.org/index.php/topic,18511.msg237522.html#msg237522
the thread is a mix of other issues as well, not being able to create a backup in windows GUI or CLI when using --data-dir ... also 0.9.3 GUI did not use the data-dir when specified.
I was able at least to get a backup when using GUI with all data kept in default appdata directory but the wallet_export_keys does not create a json file on windows or linux.
Obviously this works for some people but not for me. I can only guess maybe it is to do with too many accounts or too many keys. (20 account, many with 30,000 or more generated keys) I've also always had issues with the transaction history never showing with this wallet, i presume due to some corrupted transaction memo. just guesses, i don't know what else could cause it.
The text was updated successfully, but these errors were encountered: