Closed TalipV closed 8 months ago
I made changes in https://github.com/enisn/UraniumUI/pull/591 that probably solves the problem but I couldn't make sure.
How can I reproduce the problem? Do you have reproduction steps?
I made changes in #591 that probably solves the problem but I couldn't make sure.
How can I reproduce the problem? Do you have reproduction steps?
My app has an AutoCompleteTextField at its MainPage and my app is kept alive through a persistent notification. I can reproduce it when I close and reopen the app. 2.8.0-pre.5
It was working fine on my app when I pulled the branch"2.8-autocompleteview-handler-fix" and directly referenced it. So I guess your change was good. Thanks a lot!
Thanks for the feedback, it'll be released in the next release.
In AutoCompleteViewHandler.Android the DisconnectHandler-override causes an exception when get_PlatFormView is called: InvalidOperationException - "PlatformView cannot be null here"
This occurs sometimes when I start my app and crashes the whole thing.
The reason seems to be that when the base, Microsoft.Maui.Handlers.ElementHandler, triggers DisconnectHandler it sets the PlatformView intentionally to null beforehand because "PlatformView access should be isolated to the instance passed into DisconnectHandler".
All it takes to fix this seems to be using the parameter "platformView" in AutoCompleteViewHandler.Android
Maybe I am missing something as I am not that experienced with this stuff.
Here is the the exception: