FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
98 stars 17 forks source link

View reload each time I switched back to the app on MacOS #2855

Closed ustikya closed 1 week ago

ustikya commented 2 weeks ago

Has your issue been reported?

Current Behavior

MacOS. Use the full-screen app, switch to the emulator to test the app, switch back to FlutterFlow, and see the loading animation. After this, the app "loses" the emulator status. It cannot see that the app is running.

Expected Behavior

No loading screen or saved state of the emulator after switching back to the app.

Steps to Reproduce

  1. Go fullscreen
  2. Launch the app in test mode on the emulator
  3. Switch to the emulator to test the app
  4. Switch back to FlutterFlow app

Reproducible from Blank

Bug Report Code (Required)

ITESz/Hqx89gocdJ1anTKsZQhQAkQzM8bYJMl9dTRUsgfZzvE7Mider+VFNvOcuzYAtUE1magXExpdrHvtr1EO4VCE2CUoNowbpAYRbJUTmhb8ybO7ueSGpfGtJUFXKG4J+Jvx55CMB1SEJnw1r/cq3qNleeY8aSfxBlZ7vfcPo=

Context

I am just trying to use the app and this issue becomes annoying.

Visual documentation

Screenshot 2024-05-03 at 21 29 46

Additional Info

No response

Environment

- FlutterFlow version: 4.1.46
- Platform: iOS
- Browser name and version: Chrome 124.0.6367.119 (Official Build) (arm64)
- Operating system and version affected: MacOS 14.4.1 (23E224)

General

Relative to the time the changes were made, data was lost within

When following my steps to reproduce, data loss happens

ignalauret commented 2 weeks ago

Hey @ustikya thanks for your report. We have already got a complain about this new reload on MacOs, so the technical team is already checking it. I will link your issue to the internal ticket so they keep you updated when it's fixed.
To avoid confusion, I'm closing this ticket as duplicate. Have a great day!

ignalauret commented 2 weeks ago

Reopening issue and marking the other one as duplicate, since this one is public and can help anybody else that is getting the same experience.

leighajarett commented 1 week ago

Thanks for this! The issue has been resolved and should be deployed to production soon