search

reactiveui / Sextant

A ReactiveUI navigation library for Xamarin.Forms
MIT License
157 stars 26 forks source link

[BUG] PushModal does not allways show View #544

Closed Flying--Dutchman closed 2 years ago

Flying--Dutchman commented 2 years ago

Describe the bug

From our users we get the info that sometimes the modal views aren't being pushed onto the stack. As in, calling the modal view doesn't seem to do anything. We were able to reproduce the issue only once and that without any exception. It's very strange since it does happen on multiple devices, mostly older devices, but only on very rare occasions and after a new start of the app everything is working fine.

We also received the info that one user experienced the bug that, although the called modal view isn't visible, the app appears unresponsive.

I know this isn't much information, but maybe someone has experienced the same, or someone has any idea or hint why this happens.

RLittlesII commented 2 years ago

@Flying--Dutchman If you can provide a reproduction, or maybe even a code snippet showing how you are consuming it, it would definitely help.

Also. Some of the information in the bug template is useful to understand your particular problem, i.e.

Environment

Flying--Dutchman commented 2 years ago

We currently only have Android builds; The bug appeared on different Samsung devices and a Pixel C tablet. We're calling the new ViewModel with:

ReactiveCommand.CreateFromObservable( () => ViewStackService.PushModal<PlaceholderViewViewModel>());

Version: Xamarin.Forms: 5.0.0.2012 ReactiveUI.XamForms: 13.3.2 Sextant.XamForms: 2.12.4

RLittlesII commented 2 years ago

@Flying--Dutchman Did you try adding an output scheduler to the ReactiveCommand.CreateFromObservable?

Flying--Dutchman commented 2 years ago

I'm very sorry. Did just write my bachelor thesis and had zero time for my app. I will test next week with adding an output scheduler. Thank you

Flying--Dutchman commented 2 years ago

As it seems we are currently unable to reproduce this issue, even without an output scheduler. I'll keep an eye out and report back if it happens again.

Thank you for your help :+1:

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.