Cannot login to my wallet

[yousufdarr]

Not sure exactly the chain of events that caused this to happen but I went to send some LTC to my account from Kraken. Switched back to the main Cake Wallet app and I can no longer enter my pin and login to my wallets.

It could have something to do with the fingerprint being enabled. I can't really share any more info apart from these two errors. The first one came from v4.4.1 and the second one from the latest v4.5.0

Couldn't see any other issues listed that seem to be having this problem, so I decided create one.

[SamsungGalaxyPlayer]

Thanks for the report! The fastest way forward is to restore from seed. If you can wait a while, we'll try to get over a special diagnostic build.

[benhall847]

I think I can shed some light on this -

correct me if im wrong

But I have ran into this issue many times.

It seems if you are using a phone with a removable battery (or maybe simply a phone that runs out of battery)

If the phone is abruptly shut-off while the wallet is syncing - you will no longer be able to open the wallet & are forced to restore the wallet from seed.

[benhall847]

I actually just confirmed & recreated this issue (or one very similar)

Steps to Reproduce:

1. Open an older wallet so that it needs to sync

2. While the wallet is mid-syncing (I waited to see the # of blocks go down a bit) - remove the battery of the phone. (or abruptly turn it off if you can - but id recommend using a phone with a removable battery for easy reproducing of the bug)

3. Restart the phone & open the Cake Wallet

4. Enter your wallet PIN

result: "ERROR: input stream error"

Expected result: wallet is opened & continues to sync

[yousufdarr]

Can you send a screenshot of the error so we can see what it says exactly since as you can see neither of my errors are InputStream errors?

My phone isn't really either of those, battery life is great and it isn't removable. I don't have the seed for this wallet unfortunately as when it came up I switched screen to my Kraken, sent some money over and then I couldn't get back into it.

At the very least this is a small nudge for the diagnostic build @SamsungGalaxyPlayer so I could start trying to look into this myself potentially. Thank you

[benhall847]

I understand its not the exact 'error message'

Yet the behavior of the bug is the same (and at least this provides some reproducible steps)

I wonder if the android system itself could cause the same bug in a different way ie - abruptly stopping the Cake Wallet app while it was mid-sync & end up with a different 'error message'

[yousufdarr]

Just a gentle nudge here. Any chance of that diagnostic build anytime soon? @SamsungGalaxyPlayer

[OmarHatem28]

@yousufdarr we have it ready for Android, this build will display the Seeds for your current wallet after entering the correct PIN code, so you can copy it and restore the wallet in a fresh install.

for anyone with the same issue on Android please send your Google Play account to support@cakewallet.com while mentioning the issue and that you would like to receive the internal build for showing the seeds, so we can add you to this build track and send you the steps needed to install.

The rest of the errors included in this issue should be obsolete and not in the newest versions. Thanks for opening the issue and providing potential ways to replicate

[yousufdarr]

Hi @OmarHatem28

Thanks so much for getting back to me with this great news. I'll send an email to support now to sort this!

Y

[yousufdarr]

Unfortunately I’m still unable to get into my wallet. Same error as I was receiving before. Installed the internal testing build.

Have also tried to use adb to remove the application without removing local data. But this did not fix the issue so maybe it’s something to do with the data I have stored on my local device is corrupt in some way?

It could possibly be related to these permissions:

android.permission.USE_FINGERPRINT android.permission.USE_BIOMETRICS

Would it be possible to get a build which would show my seeds in the toast above?

[OmarHatem28]

Unfortunately, if the stored data is corrupted, there is probably nothing to do about that, as we don't save any user info and all of that is stored on the user's device, the trial APK (internal testing build) is just bypassing some of the corrupted data and just search for the stored seeds and show them to the user, but if it didn't do so, then unfortunately the seeds might be corrupted as well.

for future enhancements, could you please share more info on why you think the stored data was corrupted, like, do you have some cleaning/boosting app on your mobile device that might alter applications files? did this happen after a software update for instance? what's the device type and/or software info? (of course, feel free to share the info you want on support@cakewallet.com if you don't want to share it here)

[yousufdarr]

Hi @OmarHatem28 coming back to this after 6 months, when I put my passcode I do receive an object. However it does have a lot of unicode escape characters. I'm wondering if this is on my device or due to conversion.

It happened when I went to send some of my coin to another account. Possibly I turned on biometrics in between and then when I went to go back into I started seeing that original toast message.

I have some hope yet that the message could be decoded since some of it is readable but other parts are not