| Summary: | Android app crashes immediately on starting | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Iyán Méndez Veiga <me> |
| Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | 7429c5c9, aleksandarbayrev, andrew.g.r.holmes, b.point.c, baljit_sanghera, cameronmyers687, chandanpanda478, czl92783719, daiajo, deepangad14, driverelectro6700, ekonom1, elijahblake0, frapox, fursumsum, G1337663816, gnome, jke, justin.myers600, kde, kde, kde, kde, kdebugs, kdebugs, kjathome, kylepcondon, mad.scientist, mail, matthew, michal, mike, moamenpm, muellhalde, mully_cap, o.freyermuth, p.r.worrall, philippe.roubach, sangei12, shortyreusser, sp1rit, sranderson, sudhegan, tkk13909, tutul, u359im+45leykikibzdf9ft1o, vamp898, william.f.s.bake, william.full.moon |
| Priority: | VHI | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Android | ||
| OS: | Android 14.x | ||
| URL: | https://invent.kde.org/network/kdeconnect-android/-/commit/63d1d15c4fb02dadf0a28ad3358150e14970f94d | ||
| Latest Commit: | Version Fixed In: | 1.32.5 | |
| Sentry Crash Report: | |||
| Attachments: | Android crash log | ||
Probably this commit https://invent.kde.org/network/kdeconnect-android/-/commit/283956c10767b9313919af29e3029691c572a616 is the culprit. Had the same behaviour. A restart of the mobile was necessary. Now the app starts but won't find the KDE Session. Indeed the above commit broke the app on Android 14+, this should fix it: https://invent.kde.org/network/kdeconnect-android/-/commit/63d1d15c4fb02dadf0a28ad3358150e14970f94d I'm going to make a new release with the fix. Thanks for the quick fix Albert ;) *** Bug 493953 has been marked as a duplicate of this bug. *** *** Bug 493985 has been marked as a duplicate of this bug. *** *** Bug 493983 has been marked as a duplicate of this bug. *** *** Bug 493958 has been marked as a duplicate of this bug. *** *** Bug 493961 has been marked as a duplicate of this bug. *** *** Bug 494006 has been marked as a duplicate of this bug. *** *** Bug 494009 has been marked as a duplicate of this bug. *** *** Bug 494016 has been marked as a duplicate of this bug. *** *** Bug 493958 has been marked as a duplicate of this bug. *** *** Bug 494030 has been marked as a duplicate of this bug. *** *** Bug 494027 has been marked as a duplicate of this bug. *** *** Bug 494021 has been marked as a duplicate of this bug. *** *** Bug 494022 has been marked as a duplicate of this bug. *** *** Bug 494024 has been marked as a duplicate of this bug. *** *** Bug 494028 has been marked as a duplicate of this bug. *** How long does it take normally for Google to distribute the update in Google Play? Almost all people with recent smartphones are affected by this issue and creating duplicated reports or leaving bad reviews in the app store :( Also, I just checked and F-Droid also still didn't receive the update either. Is there some alternative place where users could get an updated apk package? *** Bug 494035 has been marked as a duplicate of this bug. *** *** Bug 494035 has been marked as a duplicate of this bug. *** *** Bug 494037 has been marked as a duplicate of this bug. *** (F-Droid 1.32.3 seems to be behind even Play Store 1.32.4) (In reply to Iyán Méndez Veiga from comment #20) > How long does it take normally for Google to distribute the update in Google > Play? From my experience with my own apps, it can sometimes take a few days. It seems very rare that an update goes out quickly, though I think there's a degree of random luck about it. I suspect that given the sort of permissions KDEConnect has, it may get more intensively checked. And then, unfortunately, there's the question of how quickly people's devices pick it up. Looking at the Play Store listing, my guess is that you pushed the last APK out on September 28th. My 'phone only got updated with it yesterday, so you may be looking at a delay of something like four days. *** Bug 494039 has been marked as a duplicate of this bug. *** *** Bug 494042 has been marked as a duplicate of this bug. *** *** Bug 494047 has been marked as a duplicate of this bug. *** TEMPORAL FIX: Disable keyboard entry on both devices then disable "Receive remote keypresses" and "Remote Input" plugins, after that the app will stop the crashing. *** Bug 494060 has been marked as a duplicate of this bug. *** *** Bug 494064 has been marked as a duplicate of this bug. *** *** Bug 494026 has been marked as a duplicate of this bug. *** *** Bug 494068 has been marked as a duplicate of this bug. *** *** Bug 488959 has been marked as a duplicate of this bug. *** *** Bug 494085 has been marked as a duplicate of this bug. *** *** Bug 494070 has been marked as a duplicate of this bug. *** *** Bug 494074 has been marked as a duplicate of this bug. *** *** Bug 494084 has been marked as a duplicate of this bug. *** *** Bug 494087 has been marked as a duplicate of this bug. *** I was just a second away from reposting this bug. Thank god i'm not the only one. if it helps in any way, here's a logcat of the crash. https://paste.crdroid.net/kGVP8v *** Bug 494091 has been marked as a duplicate of this bug. *** *** Bug 494092 has been marked as a duplicate of this bug. *** V 1.32.2 (Sep 12, 2024) from F-Droid store runs well. The problem begins with 1.32.3 *** Bug 494107 has been marked as a duplicate of this bug. *** *** Bug 494109 has been marked as a duplicate of this bug. *** *** Bug 494116 has been marked as a duplicate of this bug. *** *** Bug 494113 has been marked as a duplicate of this bug. *** it crashes only when connected to devices, if no device is connected it doesn't crash, android app version 1.32.3 ( installed from f-droid) Updated to 1.32.3 today, app no longer works. When i delete data, it works until i pair. Pairing works on the Desktop, but has no effect on the Smartphone, it still says not paired and crashed shorty after and can no longer be opened afterwards (instant crash) *** Bug 494112 has been marked as a duplicate of this bug. *** *** Bug 494113 has been marked as a duplicate of this bug. *** For all, and sudhegan@gmail.com in particular: This issues has been fixed in version 1.32.5 (check the link to the patch above in the comments from Albert some days ago) , that is why this is marked as solved. But this version is still not available in the usual app stores (Google Play and F-Droid). It takes some days since the new version is uploaded until it gets approved by Google and is distributed to everyone. Thanks for the fast reply! I assume it won't land in the KDE Android Release Builds Repository for F-Droid to get it faster? *** Bug 494117 has been marked as a duplicate of this bug. *** (In reply to Jonathan Osiel Hernandez Escobedo from comment #29) > TEMPORAL FIX: Disable keyboard entry on both devices then disable "Receive > remote keypresses" and "Remote Input" plugins, after that the app will stop > the crashing. This worked for me as a temporary workaround. Thanks. *** Bug 494126 has been marked as a duplicate of this bug. *** *** Bug 494133 has been marked as a duplicate of this bug. *** *** Bug 494131 has been marked as a duplicate of this bug. *** *** Bug 494136 has been marked as a duplicate of this bug. *** The new version is now available on the Play Store. And I'm pleased to report that it works! *** Bug 494163 has been marked as a duplicate of this bug. *** The new version, installed from Play Store, fixes the issue for me, thanks! F-Droid doesn't have it yet, FYI *** Bug 494172 has been marked as a duplicate of this bug. *** *** Bug 494189 has been marked as a duplicate of this bug. *** The new version is also available now (2024.10.5) on F-Droid. On 10/4/24 21:47, Tony Green wrote: > https://bugs.kde.org/show_bug.cgi?id=493943 > > --- Comment #60 from Tony Green <kde@web-brewer.co.uk> --- > The new version is now available on the Play Store. And I'm pleased to report > that it works! > *** Bug 494275 has been marked as a duplicate of this bug. *** |
Created attachment 174307 [details] Android crash log SUMMARY I just got an update to 1.32.4 via Google Play, and the app does not even start, it crashes immediately. Something is very wrong with this last release. STEPS TO REPRODUCE 1. Try to open app OBSERVED RESULT App does not start EXPECTED RESULT Best Android app running happily again :) SOFTWARE/OS VERSIONS Google Play: 1.32.4