Fail to format date to a string when using `android.text.format.DateFormat` in a minified build. [267194806]

Assigned

Bug

[AOSP] assigned

Status Update

No update yet.

Description

st...@gmail.com

created issue #1

Jan 31, 2023 09:33AM

I got a Pattern of "MMMM" and my Locale is "en_SE" (locale is irrelevant as far as I could tell from testing)
When I pass my pattern to DateFormat.getBestDateTimePattern(locale, "MMMM"), I get back the string "LLLL"

However then, for a function:

fun getString(pattern: String): String {
  val formatter: DateTimeFormatter = DateTimeFormatter.ofPattern(pattern, locale).withDecimalStyle(DecimalStyle.of(locale))
  return Instant
    .ofEpochMilli(utcTimeMillis)
    .atZone(utcTimeZoneId)
    .toLocalDate()
    .format(formatter)
    .also { println("$pattern -> $it") }
}

When I call this like this:

getString("LLLL")
getString("MMMM")
getString("MMM")
getString("MMMM yyyy")
getString("yyyy")

I get the output of

LLLL -> 1
MMMM -> January
MMM -> Jan
MMMM yyyy -> January 2020
yyyy -> 2020

So it turns my "MMMM" locale to "LLLL", and then when passing it through LocalDate.format(formatter) it fails to parse the string. Resulting in the string "1" instead of "January" as I want it to be, and as "MMMM" prints out.

The very important bit here is that this only happened in production, and from testing I realized it happens specifically when I got minification enabled in gradle (minifyEnabled = true).

I don't know if this is an issue with the DateFormat.getBestDateTimePattern returning the wrong thing, or how minification makes only that one fail but not the "MMMM" case. Any ideas here?

Comments

vi...@google.com <vi...@google.com> #2Jan 31, 2023 11:48AM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Expected output
What do you expect to occur?

Current output
What do you see instead?

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

NOTE: Please upload the files to Google Drive and share the folder to android-bugreport@google.com, then share the link here.

jo...@cmoney.com.tw <jo...@cmoney.com.tw> #3Apr 22, 2024 03:45AM

ok, I did some more research, turns out that callback notification goes to the if we press "cancel" button but goes wrong when authentication succeeds

as you can see in the attached project
if you open the bio-prompt in the 1st Fragment and authenticate
and after that you go to the 2nd Fragment and authenticate in the bio-prompt
callback notifies the Fragment1 instead of the Fragment2 as you can see in the logs

expected result is that Fragment2 is notified instead of Fragment1

also if you first go to Fragment2 and after that you go to Fragment1 always opening the prompt and doing the authentication
Fragment2 is notified instead of Fragment1

funny thing is that doing cancel instead of authentication notification works ok

https://drive.google.com/open?id=1ZVhp9sFBJ6pa1bKzHg1AM5tF5XnmyFMM

Issue 267194806

Description

Issue summary

Comments

vi...@google.com <vi...@google.com> #2Jan 31, 2023 11:48AM

jo...@cmoney.com.tw <jo...@cmoney.com.tw> #3Apr 22, 2024 03:45AM

Add comment

Issue metadata