Old flet client app versions do not launch on Mac

[mikaelho]

Have repeatedly seen the following behavior on Mac:

• I get this error when trying to launch a flet app in "local app mode":

  The application cannot be opened for an unexpected reason, error=Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x60000374d650 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}

• Web mode works normally.

• When I check flet version, I see that there is a new version available.

• After upgrading to latest version, app launches normally.

While this is in a way great, as it keeps me motivated to quickly upgrade to the latest version, it is not good for stable application use.

Speculation: Mac only considers the latest flet Flutter client app valid.

Would be great if anyone else using a Mac could verify this behavior.

[mrkito]

just reinstall flet)

[mikaelho]

just reinstall flet)

Sorry, I do not understand what you mean. flet apps cannot stop working just because a new version of flet is released.

[FeodorFitsner]

I'm testing in a virtual environment. Apple M1. Just did pip install flet --upgrade to 0.1.48, had 0.1.46 before.

Was able to run sample app without any issues and with Flet and fletd in correct locations:

[Screenshot]

In the same time there is still Flet 0.1.46 in the temp folder:

(venv1) feodor@Feodors-Mac-mini 4 % ls /private/var/folders/66/jrqkzks15q76d85xhkqlwm680000gn/T/flet-*
/private/var/folders/66/jrqkzks15q76d85xhkqlwm680000gn/T/flet-0.1.46:
Flet.app

/private/var/folders/66/jrqkzks15q76d85xhkqlwm680000gn/T/flet-0.1.48:
Flet.app

[mikaelho]

Thanks for the effort!

The issue I was describing is that when you next release 0.1.49, the app that now runs fine on 0.1.48, stops working (without any changes or updates).

Virtual machine might not give an accurate result if you restart it between now and then.

Next time when this happens for me, I will try restarting the machine instead of installing the latest version.

[FeodorFitsner]

I meant it was Python's virtual environment, in a separate folder. I'm testing on a physical machine.

OK, let me check an a different Mac with Intel CPU.

[FeodorFitsner]

Tested on another Mac - it still works with an old 0.1.39 installation:

[dsgibbons]

Would be great if anyone else using a Mac could verify this behavior.

Same happened to me on Mac today. Upgrading also fixed the issue for me.

[mikaelho]

Thanks @dsgibbons, this helps. In order to help pinpoint the cause, could you share which editor and package manager are you using?

PyCharm and poetry for me.

[FeodorFitsner]

Could be related: #181 (comment)

[dsgibbons]

Thanks @dsgibbons, this helps. In order to help pinpoint the cause, could you share which editor and package manager are you using?

PyCharm and poetry for me.

@mikaelho pip/venv, editing on VSCode, and running on bash terminal

[mikaelho]

And one more thing, I am using M1, wonder if that has something to with this? Is the app compiled for M1 or are we emulating Intel?

[dsgibbons]

@mikaelho I'm using a 2015 MacBook Pro so no M1 here.

[FeodorFitsner]

@mikaelho It's build for Intel, so it uses Rosetta on M1.

[mikaelho]

New flet 0.1.50 version.

Same error.

Without installing the new version, I tried manually launching the latest version I had installed:

% open /var/folders/qn/01t1th0j6s79l1bjbqjlrvbw0000gn/T//flet-0.1.49/Flet.app

Same error.

Noticed that I only had 0.1.48 and 0.1.49 in the temp dir, so tried if removing the 0.1.48 directory changed anything.

Same error.

Then tried the launch services registering thing, and tried running again:

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -f /var/folders/qn/01t1th0j6s79l1bjbqjlrvbw0000gn/T/flet-0.1.49/Flet.app

No errors from registering call.

Still the same error.

Updated flet. My test app launched normally, after which flet-0.1.50 directory was created, and also open from the command line worked, opening the empty app.

[FeodorFitsner]

As it somehow "knows" there is a new version available? :-/