25
update issues
(lemmy.ca)
Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Make GitHub issue with full logs
Ive gone over the logs, will upload soon, have to create git account.
Strangely, there is a new pid created for each update. There's no log for the current update. Only last crash which used a different pid.
There is a line though, which says:
java.lang.IllegalArgumentException: Key "xxxxxxx" was already used. If you are using LazyColumn/Row please make sure you provide a unique key for each item.
There is a new PID for each new execution of any app. On device restart most logs go away from experiences just the error levels ones remain for some time.