Is that with the latest code? You shouldn't be seeing missing transactions when force quitting as saving the wallet occurs once a transaction is received (see the bottom of the Wallet.receive method).
The only time I know of when you can get an ECKey with a creation time of zero is when it was imported from some source that doesn't provide a timestamp. Otherwise I haven't seen that issue. If you can find a way to reproduce it, file a bug.
Topic: key.getCreationTimeSeconds() gives 0 (Read 1242 times)
the wallet was only be created and manipulated by bitcoinj.
But it been used during/for development...
I've also saw some problem when force quitting the app/bitcoinj layer so the autosave-task could not start/complete. This sometimes ended up in missing transactions.
But it been used during/for development...
I've also saw some problem when force quitting the app/bitcoinj layer so the autosave-task could not start/complete. This sometimes ended up in missing transactions.
Where did the key come from originally? I haven't heard of this issue before, encryption only touches the private key bits so the creation time shouldn't be impacted.
Hi
After playing around with a wallet (it's encrypted now), i get 0 when loading the key.getCreationTimeSeconds().
The wallet works fine, can spend coins, and there is only one key in it.
Any ideas why key.getCreationTimeSeconds response always 0?
Was the information got lost somehow?
Or is this a normal behavior for encrypted wallets?
thanks
After playing around with a wallet (it's encrypted now), i get 0 when loading the key.getCreationTimeSeconds().
The wallet works fine, can spend coins, and there is only one key in it.
Any ideas why key.getCreationTimeSeconds response always 0?
Was the information got lost somehow?
Or is this a normal behavior for encrypted wallets?
thanks
Jump to: