screenshot mirror issue on some android device

[mobarak6amtech]

After taking a screenshot, the image appears mirrored on some devices (Techno BE8).

Flutter SDK - 3.29.0

How can I fix this?

[affan3699]

Yes facing same issue on samsung A04

[hansmboron]

I'm having this problem too on Android 15 devices

[kimhak-jtrb]

I'm facing same issue

[danilosilva0]

Same here

[lukemmtt]

Same here. I did some research, seems that this issue was introduced with Flutter 3.29.0 with Impeller:

• [Impeller] GLES y axis adjustment can leak out of renderer when data is readback. flutter/flutter#163315
• Screenshot & Shader Effects result in flipped output on certain android devices (v3.29.0) flutter/flutter#163521
• [Impeller] ensure that OpenGL "flipped" textures do not leak via texture readback. flutter/flutter#163501
• [CP][Impeller] ensure that OpenGL "flipped" textures do not leak via texture readback. (#163501) flutter/flutter#163667

It only affects specific Android devices.

Fix landed in master channel flutter/flutter#163501
Cherry-pick PR not yet merged flutter/flutter#163667, should be included in 3.29.1

Workarounds:

• disable impeller, or
• downgrade to Flutter 3.27.4, or
• switch to master channel, or
• use Flutter 3.29.1 when available.

[lukemmtt]

If anyone has an affected device and is willing to test, I used AI to whip up a workaround, which uses a platform channel to check for the known-problematic GPU and if detected, applies a transformation to fix the image by flipping it. You can give it a shot by adding this to your pubspec.yaml:

  screenshot:
    git:
      url: https://github.com/TimeFinderApp/screenshot
      ref: e8eef03c9e1737a5a5355ab0fa69701926ab11b7

I've tested on iPhone, Mac, and Pixel 7 (unaffected platforms) and the workaround plugin works as usual; now I just need to know if it actually fixes the issue on affected platforms. (I do not have an affected device—the issue was reported to me by a user of my app.)

(Link to workaround repo)

[lukemmtt]

FYI this issue should be closed, as it has been resolved this week with the release of Flutter stable hotfix 3.29.1.