client: Android App Error: Failing to load previous link ID after first 24 hours
I downloaded the Android app and it worked great for about 24 hours (maybe less) and now when logging in it give me this error message.
Error: tried to load previous link ID XXXXXXX, but link not found
Logging in works great online but have not tried the desktop app since I’m in the office.
I did see a similar issue here on GitHub but was not exactly the same wording/language: Bug 7262
FWIW: I did restart the app, tired on LTE and not wifi, and rebooted my device to no avail.
If you need any more information I’m happy to provide.
About this issue
- Original URL
- State: open
- Created 7 years ago
- Comments: 16 (3 by maintainers)
hey guys, sorry about this, known bug, fixed in the next release. definitely nuking your cache is a workaround.
cc: @oconnor663 and @malgorithms
Great news, thanks for your patience!
Just got the update on my device and login works without a hitch! Thank you so much for being so open with this issue!
Four Errors of the Same Issue
@jrswab Yes I should have been more specific you have to delete your data. Kind of like in Linux when you have an new program and the whole UI gets hosed because you did something that you have no idea what you did and you can not find out how to reverse… You just delete the hidden files associated with the application and restart back to square one.
@maxtaco This is great! I am glad that my testing can help to improve this whole ecosystem. I’ll try to break it more! I’m imagining that the futurism of this is that you have a public verifiable ID and you have the ability to control how you are communicated with. Duh I know it is nothing new but you all seem to have pulled it all together quite nicely. I want to contribute as much as I can.
@ogfomk I don’t know as much about PGP as I should. Most of my encryption knowledges comes from my intense 6 month study of bitcoin about two years ago. My motherboard fried and now I have to pull my hard drive out to get my ‘paper’ key. (should have printed that out or something lol) I love security and being apart of beta tests so this is all right up my alley hahaha
I did seem some text in a shell like fashion myself once or twice. That being said it sounds like they know what is happening on the app and it will be fixed soon enough.
@jrswab The very first time I tried this whole Keybase thing out I started on phone. When the link ID error happened I was in a heap of trouble so I installed the Linux version since I could log on via the web. That is how I was able to recover. I am having quite a learning curve here as I am PGP/Encrytion challenged.
That being said, I am trying to replicate the problem so that I can upload some photos and show what I saw. There was also some shell text too! I could not make a screen shot due to app security… Now I am thinking maybe there should be a development mode that allows this? Also maybe a way to send log files when you can not log back in?
@ogfomk Deleting data and cache worked. I just wanted to test but will have to wait for the push if/when the error happens again. I don’t need a bunch of phone devices to revoke haha
Thanks @jrswab for the report. We have a fix in the latest build, we just have to prepare and push out a relese. Thanks!