Text and screen stretch issue on Android 15 when using Get.to() — occurs on background-to-foreground transition

[HARSHILITALIYA16]

I’ve encountered a visual distortion issue specifically on Android 15 devices when using Get.to() for navigation. On resuming the app from background to foreground, the active screen becomes stretched, and in particular, Text widgets appear visually stretched or distorted.

📱 Devices Tested: Vivo Y200 (Android 15)

2–3 other Android 15 test devices

The issue seems to be isolated to Android 15 and is not reproducible on lower Android versions (Android 14 or below).

** Steps to Reproduce:** Use Get.to(() => DishDetailScreen(dishId: 6)) to navigate to a screen.

Minimize the app (put it into the background).

Restore the app from the background.

Observe that the text or screen layout appears stretched or distorted.

✅ Expected Behavior The screen and text should render normally when the app returns to the foreground, maintaining their layout without any scaling/stretch artifacts.

❌ Actual Behavior After returning from background to foreground:

The text appears stretched or scaled incorrectly.

The layout seems to break, but only on screens navigated using Get.to(). example:

** ❌ Actual Behavior: *After returning from background to foreground:

The text appears stretched or scaled incorrectly.

The layout seems to break, but only on screens navigated using Get.to().**

** Tested Comparison** When I replace the Get.to() call with standard Flutter navigation:

Navigator.of(Get.context!).push( MaterialPageRoute(builder: (_) => DishDetailScreen(dishId: 6)), );

✅ The issue does not occur. ✅ Text renders normally even after background-to-foreground transition.

This strongly suggests the issue is linked to GetX’s navigation layer under Android 15.

📝 Additional Notes The issue does not occur on all screens where Get.to() is used, but it does appear consistently on specific screens.

I have a video recording demonstrating the issue — please let me know how to share it for further debugging.

https://github.com/user-attachments/assets/0c906164-48e1-4be7-90d1-995a818fb669

[kjm0202]

How about just disabling Impeller?

[shamimcse1]

I faced the same issue. After downgrading the Flutter version from 3.32.7 to 3.27.2, it's working fine now.