Client: Android app crashes after naming device

[ricklupton]

Android version 4.2.2
Keybase version 1.0.0-alpha-2

I signed into my Keybase account using my username and my desktop device. Adding the code worked ok. I named the device and clicked continue, then the app crashes.

If I reopen it, I can see that the "Phone" device has been created (it's in the list of devices to use for signing in, along with the desktop and the paper key) but it doesn't seem to be associated with the app.4.2.2.

I revoked the device and tried again, but the same thing happened.

[techmagus]

Experiencing the same. Works fine with Android M but not Jellybean.

Maybe Jellybean support can be dropped altogether, and concentrate on KK, M, N, and Android O? (My Jellybean phone is only serving as secondary/backup.)

[maxtaco]

@techmagus can you push the Gear > "Send Feedback" and send up your logs? We can take a look, thanks!

[ricklupton]

@maxtaco I can't get as far as seeing a gear icon -- the options are just "create an account" and "log in". As I described above, I tried logging in but the app crashes. Is there another way of sending the logs?

(I'd definitely like to see Jellybean support kept as I'm still using it!)

[maxtaco]

cc @cjb

[cjb]

Perhaps best for us to just try to repro the bug ourselves in a Jellybean simulator, I'll add an internal bug report to do that.

(Haven't reached an opinion yet on how much effort we should put in to supporting Jellybean.)

[berkes]

Any progress on this? Anything we can do to help?

[specious]

Same here. Android app crashed immediately after entering text verification code and now won't let me log in even though the device is listed as verified.

Android 4.2.2 on GT-I8200.

What can I do to help debug this?

[specious]

Submitted report from the Android.

[maxtaco]

@specious I don't think we can support that version of Android, I think it's too old. I hope the keybase app didn't cause your screen to crack BTW!

[specious]

@maxtaco, I absolutely concur that this Android is too old to officially bother supporting. Isn’t it curious though, that it’s possible to have a device that is listed as verified and yet it cannot log in? How is that happening?

[maxtaco]

My guess is that the app crashed when trying to store the secret key to the Android keystore, and now the app can't read the private key back out. So it got most the way through the provisioning process, but died when trying to access the key material.

[berkes]

@maxtaco and @specious It makes sense to not support this version of Android. Especially since it essentially is not supported right now.

But in that case it should be limited on the play-store/f-droid and/or the AndroindManifest.xml.

That would keep people (like me) with an old device from trying to install it, and getting a crash. Which is far more annoying than seeing a "this app is not compatible with your device", which I am kinda used to, having such an old Android.

Edit: My Android Dev-skills are too poor to make an actual PR which sets limits in the AndroidManifest.xml, so sorry that I cannot contribute other than yet another comment.

[maxtaco]

Good point. cc: @keybase/react-hackers

[jbonhag]

Not to mention the fact that I am eating up all these great device names, and now that they're revoked I can't re-use them 😆 😢

[maxtaco]

@jbonhag can you send feedback from the app?

[jbonhag]

You bet! Sorry for not being more descriptive. I am also running a super old version of Android (4.1.2), on a secondary device. I'll send those logs over tonight.

[jbonhag]

Just sent the logs, hope they help!