Safe Args should use KotlinPoet 1.8.0 [183990444]

Fixed

Bug

androidx-bug-bounty

Status Update

No update yet.

Description

il...@google.com

created issue #1

Mar 29, 2021 11:52PM

Component used: Navigation

Version used: 2.3.4

Safe Args should upgrade to KotlinPoet 1.8.0 to ensure that the generated code handles more edge cases (via the bug fixes included in that release).

Comments

ku...@gmail.com <ku...@gmail.com> #2May 2, 2021 09:50AM

Comment has been deleted.

Message last modified on May 2, 2021 09:51AM

ku...@gmail.com <ku...@gmail.com> #3May 2, 2021 09:51AM

Comment has been deleted.

Message last modified on May 2, 2021 09:52AM

ku...@gmail.com <ku...@gmail.com> #4May 2, 2021 09:53AM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

jb...@google.com <jb...@google.com> #5May 7, 2021 12:07AM

Marked as fixed.

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

Issue 183990444

Description

Issue summary

Comments

ku...@gmail.com <ku...@gmail.com> #2May 2, 2021 09:50AM

ku...@gmail.com <ku...@gmail.com> #3May 2, 2021 09:51AM

ku...@gmail.com <ku...@gmail.com> #4May 2, 2021 09:53AM

jb...@google.com <jb...@google.com> #5May 7, 2021 12:07AM

Add comment

Issue metadata