Float argument default value [173766247]

Fixed

Bug

androidx-bug-bounty

Status Update

No update yet.

Description

fo...@gmail.com

created issue #1

Nov 20, 2020 03:46PM

Component used: Navigation Version used: 2.3.1

When i use in navigation graph float attribute with default value like this:

<fragment
     android:id="@+id/myFragmentId"
     android:name="..MyFragment">   
     <argument
         android:name="ratio"
         android:defaultValue="0"
         app:argType="float" />

</fragment>

I get this error: org.xmlpull.v1.XmlPullParserException: Type is float but found integer: 0

When i try add 'F' char like this:

<argument
     android:name="ratio"
     android:defaultValue="0f"
     app:argType="float" />

I get another error, because generated NavDirections already added the 'F' char and generated code contains:

val ratio: Float = 2FF

Comments

il...@google.com <il...@google.com> #2Nov 20, 2020 11:18PM

Assigned to jb...@google.com.

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

ku...@gmail.com <ku...@gmail.com> #3Jan 21, 2021 07:34PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

ku...@gmail.com <ku...@gmail.com> #4Jan 26, 2021 08:06PM

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> #5Jan 26, 2021 08:36PM

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 173766247

Description

Issue summary

Comments

il...@google.com <il...@google.com> #2Nov 20, 2020 11:18PM

ku...@gmail.com <ku...@gmail.com> #3Jan 21, 2021 07:34PM

ku...@gmail.com <ku...@gmail.com> #4Jan 26, 2021 08:06PM

jb...@google.com <jb...@google.com> #5Jan 26, 2021 08:36PM

Add comment

Issue metadata