Fixed
Status Update
No update yet.
Comments
jb...@google.com
ap...@google.com
Or when changing to textView.textMetricsParamsCompat still crash.
private fun setAsyncText(textView: AppCompatTextView, text: String?) {
if (!text.isNullOrEmpty()) {
val textFuture = PrecomputedTextCompat.getTextFuture(text!!, textView.textMetricsParamsCompat, null)
textView.setTextFuture(textFuture) //Crash
}
}
private fun setAsyncText(textView: AppCompatTextView, text: String?) {
if (!text.isNullOrEmpty()) {
val textFuture = PrecomputedTextCompat.getTextFuture(text!!, textView.textMetricsParamsCompat, null)
textView.setTextFuture(textFuture) //Crash
}
}
jb...@google.com
add this line :
textView.setLayoutDirection(ViewCompat.getLayoutDirection(textView));
before :
setTextFuture(....)
textView.setLayoutDirection(ViewCompat.getLayoutDirection(textView));
before :
setTextFuture(....)
Description
Component used: Core
Version used: 1.7.0-alpha02. Also affects Activity
1.4.0-alpha01and up.When using the
addMenuProvidermethods that take aLifecycle, callingremoveMenuProviderdoesn't actually remove the underlyingLifecycleObserverthatMenuHostHelperadds.This has a couple of implications:
removeMenuProvideris called when the Lifecycle is below the givenstate,removeMenuProviderdoesn't remove theMenuProviderand when the Lifecycle reaches the given state, it still gets addedremoveMenuProvideris called when the Lifecycle is above the givenstate,removeMenuProviderdoes remove theMenuProvider, but if the Lifecycle goes down and then back up again, it gets re-added.ActivityResultRegistryhandles these cases (registerwith aLifecycleOwner, then callingunregister) byLifecycleOwner+LifecycleObserverinstancesMenuProvideras the key.