Pyfa won't open on Mac

Pyfa was working fine on my Mac until I updated to the March 2020 release, I downloaded the zip file, unpacked it, deleted my old Pyfa file that I had in my download folder as I usually do, but the new file won't open. It bounces up and down on my hotbar but then doesn't open and the icon disappears without an error message.

I have re-downloaded older versions, restarted my computer but to no avail.

bplist00“TPathTDate_j/Users/ismailmohdalijinnah/Library/Logs/DiagnosticReports/pyfa_2020-01-12-003935_Ismails-MacBook-Pro.crash3A¡Â…§Nî Ñ

Could you say which was last working and first broken release, please? https://github.com/pyfa-org/Pyfa/releases/tag/v2.18.0 - this is the "march 2020" release you refer to, i believe But which release worked for you before that? Did https://github.com/pyfa-org/Pyfa/releases/tag/v2.17.2 work?

In my case, 2.18.1 was working on my Mac, but 2.19.0 is not. I just went through the update ... launched 2.18.1 which informed me of the newer version being available. After downloading 2.19.0 and following the steps mentioned above (downloaded new zip, unpacked that new zip, deleted the old app from the applications folder, copied the new app to the applications folder. Right click open in order to get past the unidentified publisher alert, and then it crashes.

I'm running on a Mac Pro (late 2013, garbage can of doom), 64GB of RAM, 6-core proc.

In my case, reverting back to 2.18.1 without reboot still works.

https://github.com/pyfa-org/Pyfa/compare/v2.18.1...v2.19.0

This is very strange because there are very few changes (except for "optimize images" pull request). Could you find the most recent log file in ~/.pyfa/ and upload it somewhere?

I reproduced the issue on my mac. There's nothing suspicious in logs. Will look into what's causing it tomorrow. But my guess would be one of:

1. Image update via "Image optimize" pull request
2. Updated libraries

I’ve got my logs if that’s still helpful. Can either post here, or drop on a file share for you to review.

@RocketCowboy it seems to be another crash, unrelated to the reporter's. See #2156 for more info.

The app uses it's own python environment on the mac, correct? It would be related to changes in the python installs locally on my mac? Coinciding with the updated pyfa not working, I've moved from a home brew python3 install to using the native 3.7.7 installer from python.org. I also setup pyenv. All happened at about the same time, but should be unrelated.

This is still broken.

It is broken on some systems, but on some it is not. The system I have (mac book pro mid-2012) is capable of launching pyfa distributives. As such, I need someone to find out what causes it not to run, or debug the issue.

I have no access to vast variety of Mac configurations, so cannot do it on my own.

Anton, what is your native language?

On Thu, Jun 18, 2020 at 12:11 AM Anton Vorobyov [email protected] wrote:

It is broken on some systems, but on some it is not. The system I have (mac book pro mid-2012) is capable of launching pyfa distributives. As such, I need someone to find out what causes it not to run, or debug the issue.

I have no access to vast variety of Mac configurations, so cannot do it on my own.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pyfa-org/Pyfa/issues/2146#issuecomment-645743967, or unsubscribe https://github.com/notifications/unsubscribe-auth/APHNND63SW4YIPQPV67CYU3RXGAVJANCNFSM4LG3W4NQ .

Russian. Why do you ask?

Because portuguese users have issues with pyfa because there's a banking security software that blocks Pyfa. But it may not be your case, nonetheless, try opening some sort of mac task manager where you can monitor software cpu usage and try opening PYFA several times to see if there is any spike in any process. It may be blocking Pyfa.

On Thu, Jun 18, 2020 at 12:40 AM Anton Vorobyov [email protected] wrote:

Russian. Why do you ask?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pyfa-org/Pyfa/issues/2146#issuecomment-645752328, or unsubscribe https://github.com/notifications/unsubscribe-auth/APHNND6666EP7AACEZ2TSODRXGEC5ANCNFSM4LG3W4NQ .

I doubt it is the same on Mac and I doubt Dato (the person who created the ticket) is using Warsaw.

I have the same problem as the OP, although I have never used pyfa before. I am running on an iMac 2017 Intel Core i7, 8 GB DDR4 RAM, Radeon Pro 580 video card; MacOS Sierra 10.12.6; we have installed Python on this computer for other needs.

I have downloaded v 2.26 to my Downloads folder, moved and run the zip file from my Desktop - pyfa is installed on the Desktop. I move the package to my Applications folder. Whether I try to run pyfa from my Desktop or Applications, I get the same behavior - it tries to run but aborts with no obvious error warning.

If I 'Show package contents' and then run and try to run the executable pyfa I get an error message in a terminal window (I copied the output to Notes and saved as pdf) pyfaRunLog.pdf

@DatoKoppla are recent versions of pyfa still not working for you? Do you know the last version that was?

@atomicSi7x7 I'm not sure if this is the same issue as the original issue since it's fairly vague. But I did find this: https://github.com/pyinstaller/pyinstaller/issues/3418

Basically, our mac builds are automatically built on TravisCI using their xcode11.3 image. This is using macOS 10.14.6, and thus, I believe, this is the earliest version of macOS that will be able to run pyfa.

This is the commit that bumped the mac image from 7.3 (10.11) to 11.2/11.3 (10.14) 003dd040d and 85e1a1bd

That was earlier this year. Looks like it may have been bumped as part of a requirement for a new matplotlib version, or perhaps it was simply an oversight?

@DarkFenX, thoughts?

Image reference: https://docs.travis-ci.com/user/reference/osx/#macos-version