Visual glitch: screen briefly flashes during back navigation from sub-pages within Overlay

Report a Bug
,
1

Team ID:

  • akwn3Pz1B8giMgQglACS

App ID:

  • 34QcomnlZ0ZA2sJ7QJ2z

Description

When using an Overlay navigation target in Glide, navigating on iOS into a sub-page and then going back causes a visual glitch. Specifically, when returning to the previous screen, the intermediate page briefly flashes over the destination screen during the back animation. This creates a noticeable flicker and breaks the expected smooth transition behavior.

This issue is also visible in the Glide Editor preview. It does not occur on desktop, likely because there is no animated transition there, which suggests the issue is tied to the mobile animation itself.

Overlay navigation is important here because it preserves the user’s position on the previous screen when navigating back (both on mobile and desktop). This makes it significantly more usable for list-based UIs. By contrast, using “Current” navigation resets the user’s position when returning to the previous screen, including on desktop. If “Current” preserved scroll position consistently across platforms, it would be a viable alternative to Overlay in this case.

How to replicate

  1. On iOS (didn’t test Android), open the app: https://animationbug.glide.page
  2. On the first screen, tap any contact in the collection (this action is set to “Show detail screen for this item” with Target = Overlay).
  3. You will be taken to a detail screen presented as an Overlay.
  4. From this overlay screen, tap the first or only company listed (this can be any action; Target can be either “Current” or “Overlay”).
  5. On the sub-page, tap the back button to return to the previous screen.

Result:

During the back navigation, the currently-viewed (sub-) page briefly flashes over the main page/screen you are returning to, creating a visual glitch.

Expected behavior:

The transition back should be smooth, with no flashing or intermediate screen artifacts.

Notes:

  • The issue only requires the initial navigation to use Target = Overlay.
  • The sub-page navigation does not need to use Overlay; it can be set to Current and the issue still occurs.
  • This appears to be specifically related to sub-page navigation within an Overlay context.
  • Reproduced in a default app with 1 configuration change - main collection action gets “Overlay” as its Target instead of “Current”.
  • Since the issue appears tied to the mobile animation (and does not occur on desktop), a potential fallback would be to disable or simplify the animation on mobile if it cannot be resolved cleanly.
  • Let me know if you need any other info. I would absolutely love to see this fixed.
1 Like