Fixed
Status Update
No update yet.
Comments
st...@baramundi.de
Thanks for the report!
ra...@google.com
The release notes documentation has been edited to clarify this change in behavior for line height.
To support non-standard text sizes, we encourage users to follow the Material design system and use a different style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified), or create a custom Typography entirely.
ra...@google.com
ap...@google.com
In my case, I have multiple font sizes in the same Text (using SpanStyle in AnnotatedString). There are legitimate reasons for this. For example, when combining Chinese and English (phonetic) together (for language-learning purposes).
st...@baramundi.de
Sorry for the delayed reply. The tests you suggested did show a problem on version alpha08 (Sometimes the jobs wasn't removed fast enouth after finishing).
But as you already provided the fix, this shouldn't be something new to you.
I attached the log files just for completeness...
I can no longer reproduce the issue on alpha09 on my devices. Thank you for your swift fix and release.
But as you already provided the fix, this shouldn't be something new to you.
I attached the log files just for completeness...
I can no longer reproduce the issue on alpha09 on my devices. Thank you for your swift fix and release.
ra...@google.com
Thanks for the confirmation.
Description
Version used: 1.0.0-alpha08
Devices/Android versions reproduced on: Moto G5s Plus, Android 7.1.1 / Huawai P20 lite, Android 8.0.0
We can reproduce a crash of the workmanager on some devices.
In our code we enqueue a UniqueWork with ExistingWorkPolicy.REPLACE, as soon as it finishes with State.SUCEEDED we enqueue it again. There is always only one job at the time.
After about 100 jobs the workmanager crashes with: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs.
It looks like the workmanager does not prune the finished jobs fast enough, and they count as 'sheduled' job, even if they are finished?
The crash is reproducible on the Moto G5s Plus and Huawai P20 lite. But it behaves very inconsistent, sometimes it occurs on the first run, sometimes only after a few restarts of the app. But we cannot reproduce it on the Pixel 2 XL or the emulator.
Calling pruneWork() before enqueue() doesn't fix the problem.
Reducing the result lifetime by calling keepResultsForAtLeast(..) doesn't work as well.
We provided a sample app which triggers the issue.