Open PureWeen opened 1 year ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
I wonder if this relates to the different behavior of Loaded
event on Android and iOs. I have Shell application with several pages.
On Android:
Loaded
event handler firesLoaded
event doesn't fireOn iOS:
Loaded
event handler firesLoaded
event always fireBasically, cross platform code needs workaround for iOs to avoid running same code multiple times. I wonder if this issue will help to make lifecycle events behavior more uniform?
This honestly doesn't feel like a "Good First Issue". It seems far too complicated for someone new to the team to even attempt.
Description
Ideally, we would key loaded/unloaded off of
didMovetoWindow
onUIView
but there's no way (AFAIK) to reach this with overriding every single view.The current implementation is fiddly and probably not reliable in all scenarios. Basically, it adds observables to various layers of the view and waits until one of those triggers to fire loaded.
https://github.com/dotnet/maui/blob/main/src/Core/src/Platform/iOS/ViewExtensions.cs#L659
Steps to Reproduce
Some thoughts
Loaded
from the firstmeasure
orarrange
call on a view (though this might mean there are some cases where loaded doesn't fire and it should). We could add this on top of the current solution to make it more robust.Link to public reproduction project repository
N/A
Version with bug
7.0 (current)
Last version that worked well
Unknown/Other
Affected platforms
iOS, macOS
Affected platform versions
ios/catalyst
Did you find any workaround?
No response
Relevant log output
No response