-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"loading the wallet" after entering pin #1381
Comments
This is similar to, if not the exact same issue I had on my phone with the most recent version. I had it setup to accept a fingerprint, which it seemed to accept but would immediately throw an error after the fingerprint reader went away: "ERROR: FormatException: Invalid character (at character
Under that error was the "Loading the wallet" message. Using either my fingerprint or dismissing that and using a PIN would yield the same FormatException error with the loading message underneath. It recognized incorrect PINs and it locked me out for a few minutes but it never let me into the wallet. I thought it was due to how my fingerprint was stored/loaded so I tried clearing them out of my phone and saving a new fingerprint. I tried installing different versions of the APK from GitHub which prompted me to "update the app" but they didn't seem to do anything. I cleared the app's cache, rebooted the phone multiple times and I was considering digging through the code to see if I could find a way to fix it but I needed access to my wallet quickly. Unfortunately, I had an issue with Cake Wallet a few versions ago where I was unable to send crypto from my wallet to another address so I had my wallet backed up already and was able to uninstall/reinstall the application and restore from that. It didn't retain any of my wallet data when I uninstalled, either. So I'm happy the backup worked. I was a little nervous considering I've had multiple issues with Cake recently and I didn't have to use the backup previously, I opted to stay locked out of my wallet until they patched the issue. Hopefully the additional info helps track down your issue. Being locked out of a wallet is terrible. |
Sorry to hear, that is very frustrating. Will be looking into this, can I get the Phone/OS version from both of you? (Sometimes OEMs do funny things that can in certain cases change behaviors) If either of you run into this problem again please try getting a logcat of the app while attempting to unlock it so we can investigate if there are any internal errors :) |
Cake Labs tech support used to be great; now they just ask did you backup
the wallet (no I didn't, did you even read my message? I'm constantly
creating new wallets because I don't think XMR is nearly as untraceable as
most believe).
After replying that I don't have a backup and there must be some way to
restore it from the data still on my phone I never get another response -
as if they won't deny that's possible but just won't help as the ability to
do that may compromise security.
I'm not nearly familiar enough with coding to figure this out on my own but
(especially considering it's open source) one of two answers must be true.
Either A) Here's how to pull the data from your phone or B) It's not
possible and here is why.
So far I haven't gotten either of those responses from cake labs.
…On Sun, Apr 21, 2024, 10:35 PM tuxsudo ***@***.***> wrote:
Sorry to hear, that is very frustrating. Will be looking into this, can I
get the Phone/OS version from both of you? (Sometimes OEMs do funny things
that can in certain cases change behaviors)
If either of you run into this problem again please try getting a logcat
of the app while attempting to unlock it so we can investigate if there are
any internal errors :)
—
Reply to this email directly, view it on GitHub
<#1381 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHZDWDTQZWYEFH6L7NXY5QLY6RZNPAVCNFSM6AAAAABGEXYK2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGM3TQMZTGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm on a Galaxy Note 20 Ultra (Android 13).
I'm fairly certain this error first occurred because the storage on my
phone was completely filled (I thought it was unlocking slowly the first
time it happened because of a storage issue & someone at reddit with the
same error fixed it by freeing up space); I've since cleared more than
enough space (100gb+) but the issue pressists for me.
…On Sun, Apr 21, 2024, 10:35 PM tuxsudo ***@***.***> wrote:
Sorry to hear, that is very frustrating. Will be looking into this, can I
get the Phone/OS version from both of you? (Sometimes OEMs do funny things
that can in certain cases change behaviors)
If either of you run into this problem again please try getting a logcat
of the app while attempting to unlock it so we can investigate if there are
any internal errors :)
—
Reply to this email directly, view it on GitHub
<#1381 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BHZDWDTQZWYEFH6L7NXY5QLY6RZNPAVCNFSM6AAAAABGEXYK2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGM3TQMZTGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Is it possible that there is a 15 word memonic? Otherwise I miss some 1 word (polyseed) and have this bug also. If i go in to other user profile (grapheneOS) cake seems to work (new wallet for test). Is it possible if you have root privileges to obtain the stored (private) keys? I have not rooted my phone and flashing is no option from the top of my head.. |
After entering my correct pin on the latest Android version a message appears that says "loading the wallet" but nothing ever happens and the app just hangs there (the program doesn't freeze, it just stays on the pin screen. Interestingly if the wrong pin is entered it recognizes that.
I'm not the first person to encounter this but. I never backed up the wallet (yes I know, stupid). But there must be a way to restore it from the info/files saved on my phone. Any help is appreciated! There's got to be a way to save this wallet.
The text was updated successfully, but these errors were encountered: