Bug: on Android 15, calling ConsentInformation.requestConsentInfoUpdate ruins fetching current dynamic-colors during runtime

[AndroidDeveloperLB]

Reported here:
https://issuetracker.google.com/issues/386855222
material-components/material-components-android#4519

[Kiro705]

Hello @AndroidDeveloperLB ,

Can you share any steps for how this can be reproduced using the Android sample apps?

Thank you,
Jackson
IMA SDK team

[AndroidDeveloperLB]

@Kiro705 Have you checked the link? It has clear steps, code snippets, video and sample.

[Kiro705]

Hello @AndroidDeveloperLB

I did look at the attached bug, but did not see mention of any of the sample apps in this repository, but the issue would likely be for the UMP example.

The example doesn't specifically use DynamicColors, so I think the sample is still functioning correctly. But I think you are pointing to a potential bug in ump.ConsentInformation, is that correct? If so, I can forward the issue to the correct team.

Thank you,
Jackson
IMA SDK team

[AndroidDeveloperLB]

@Kiro705 But it does affect DynamicColors too, and I've shown it right here:
https://issuetracker.google.com/issues/386855222#comment6

Not only that, but as I wrote, it affects all Activities. So once I call this function, it ruins everything related to dynamic colors in the entire app.
I can't think of any workaround for this other than having a new process just for this, which is terrible.