Fixed
Status Update
No update yet.
Comments
ap...@google.com
We started noticing this on Android 8 and 8.1 devices after we upgraded appcompat library from 1.3.1 to 1.4.0. Seems like that the newest library is using a different/newer classes for handling emojis.
jb...@google.com
Thanks for the report, this is a combination we didn't predict and need to resolve.
In the current version of the libraries, precomputed text won't work with the presence of emoji in 1.4.0. There is no workaround using precomputed text in the current library, so the best solution is to `setText` as proposed.
Notes for resolution (options discussed):
1. Disabling emoji processing for precomputed text from InputFilter etc
2. Integrate emoji into PrecomputedTextCompat to apply emoji processing prior to precomputation (needs research)
In the current version of the libraries, precomputed text won't work with the presence of emoji in 1.4.0. There is no workaround using precomputed text in the current library, so the best solution is to `setText` as proposed.
Notes for resolution (options discussed):
1. Disabling emoji processing for precomputed text from InputFilter etc
2. Integrate emoji into PrecomputedTextCompat to apply emoji processing prior to precomputation (needs research)
Description
Component used: Activity Version used: 1.2.0-alpha07
If you register for a result with a
LifecycleOwnerand your activity goes through process death and restoration, once it is created again if there is already result a waiting to be returned to theLifecycleOwneran observer is added to wait until theLifecycleisSTARTED. When the lifecycle owner is unregistered, the observer is never removed.We should keep track of any observers added to the
LifecycleOwnerand remove them if the callback for the lifecycle owner is ever unregistered.