IllegalArgumentException when parsing SplitAttributes.LayoutDirection from Locale.Default [312268749]

Assigned

Bug

Status Update

No update yet.

Description

je...@microsoft.com

created issue #1

Nov 20, 2023 09:51PM

Seeing the following crash in the androidx.window library

Caused by java.lang.IllegalArgumentException:
at androidx.window.embedding.SplitAttributes$LayoutDirection$Companion.getLayoutDirectionFromValue$window_release (SplitAttributes.kt:345)
at androidx.window.embedding.RuleParser.parseSplitPairRule (RuleParser.kt:181)
at androidx.window.embedding.RuleParser.parseRules$window_release (RuleParser.kt:67)
at androidx.window.embedding.RuleController$Companion.parseRules (RuleController.kt:134)
at com.myapp.ui.split.SplitInitializer.create (SplitInitializer.kt:16)
at com.myapp.ui.split.SplitInitializer.create (SplitInitializer.kt:13)
at androidx.startup.AppInitializer.doInitialize (AppInitializer.java:180)

My SplitPairRule has locale set

window:splitLayoutDirection="locale"

OnePlusT7Pro, Android 12

Comments

vi...@google.com <vi...@google.com> Nov 20, 2023 11:55PM

Assigned to di...@google.com.

ak...@google.com <ak...@google.com> Nov 21, 2023 01:46AM

Reassigned to ji...@google.com.

ji...@google.com <ji...@google.com> Nov 21, 2023 01:52AM

Reassigned to an...@google.com.

lo...@google.com <lo...@google.com> #2Nov 27, 2023 02:20PM

Reassigned to ch...@google.com.

Charles, mind help taking a look?

ch...@google.com <ch...@google.com> #3Dec 4, 2023 06:27AM

Reassigned to je...@microsoft.com.

May I know which version are you using?

ch...@google.com <ch...@google.com> #4Dec 4, 2023 06:32AM

Also, it would be helpful if you have bugreport(adb bugreport) of the crash.

je...@microsoft.com <je...@microsoft.com> #5Dec 4, 2023 05:20PM

Thanks for the attention here everybody.

AndroidX.Window version is 1.1.0

Unable to reproduce myself, this stack trace is from a Crash Report, so unable to capture a bug report... but can share more of the Stack Trace if that's helpful?

je...@microsoft.com <je...@microsoft.com> #6Dec 4, 2023 05:22PM

Also happy to update to 1.2.0 (looking through the release notes I'm not sure that this issue has been addressed explicitly)