PrismLibrary / PrismLibrary/Prism

[INavigationServiceExtensions] Using 'GoBackToAsync' cannot immediately return to the specified page

Open
#3,247 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C#
Stars
6.8k
Forks
1.6k
Avg merge
2d 1h
Merged PRs (30d)
1

Description

Description

Hi,

Assuming the known routing stack is A ->B ->C ->D ->E, I will now call 'GoBackToAsync(B)' on page E. I want to immediately return to page B, but it will return D, C, E in sequence from page E, accompanied by a brief animation. Please refer to the video for details.

I don't want animation, I expect to return to page B immediately

image

https://github.com/user-attachments/assets/c6d255c0-148e-498b-8b30-3b0b2995e39c

Steps to Reproduce

If there are multiple pages, using ‘GoBackToAsync ’ cannot immediately return to the specified page. Currently, it is accompanied by some animations, and I need to wait for 2-3 seconds for the animations to end before returning to the specified page

Platform with bug

.NET MAUI

Affected platforms

iOS, Android

Did you find any workaround?

No

Relevant log output
<PackageReference Include="Prism.Maui" Version="9.0.218-pre" />

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the GoBackToAsync implementation in Prism.Maui and reproduce the A → B → C → D → E navigation case on iOS and Android with Prism.Maui 9.0.218-pre. Compare the observed animated intermediate returns with the requested behavior; done means GoBackToAsync(B) reaches page B immediately without waiting for the intervening animations.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.