mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-25 11:45:49 +03:00
[GH-ISSUE #407] auto-py-to-exe on macOS seems to have buggy windows behavior #330
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gernophil on GitHub (Jul 12, 2023).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/407
Originally assigned to: @gernophil on GitHub.
I am using
auto-py-to-exe(version 2.36.0; installed in acondaenvironment, but usingpip) on macOS and I am experiencing some buggy window behavior. Some of it appears random, some always. I am startingauto-py-to-exewithout any additional flags and it opens normally.Window issue 1:
However, sometimes, when click on "Import Config From JSON File", the opening dialog, where I can select the JSON file does just not open. This luckily happens rarely (estimated in 1 in 30-50 attempts), but if it happens it influences my whole system. I am not able to open any open file dialog in any other app (I tried e.g. Word, Firefox, VSCode). It's really annoying and I did not find a way to solve this. Up to now it always started to work again after some attempts or reboots, but I haven't found a reproducible solution for this yet. I never experienced this with any itNext time it happens, I will copy the terminal output and see if this helps. It was something about
NS...which refers to the macOS windows system IIRC. I know it's a bit fishing in the dark with this info, but maybe it still helps.Window issue 2:
Every time I click on "Import Config From JSON File" a black square windows appears, that's on top of everything and only disappears after I close
auto-py-to-exe. This happens always (see screenshot), and it might be related to windows issue 1.Windows issue 3:
Ok, for this I am not sure, if it's related to
auto-py-to-exe, but I haven't used anything else while it happened. And this luckily happens really rare, but it did happened twice yesterday.auto-py-to-exeseems to crash my Finder. At least this happened whileauto-py-to-exewas opened, and I also never experienced that before. Had to reboot the computer completely, since I wasn't able to just restart finder. It immediately crashed again.@github-actions[bot] commented on GitHub (Jul 12, 2023):
👋 Hi, just a reminder that if you haven't read the help post yet, give it a read to see if your issue is covered in it and make sure to follow the debugging section.
Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help post, video or create a new discussion.
@brentvollebregt commented on GitHub (Jul 13, 2023):
A quick note: I do not own a Mac so am unable to do any testing myself sorry.
Question 1
If there was something in the console, this would be suuuper helpful to have 👍
Question 2
Does this look related to #304 by any chance?
If you run this script in Python, does it lead to the same issue?
Question 3
I haven't heard anything like this before, but it may be related to question 1? Not sure.
@gernophil commented on GitHub (Jul 31, 2023):
Thanks for the reply. Been on vacation the last two weeks, so I don't have any update for questions 1 and 3. For question 2 I executed your small script. This does indeed lead to such a small window too, but this is attached to the opening dialog and fully responsive (see screenshot; sidebar and files not shown for privacy reasons). I don't think it's exactly the same. The terminal output also looks normal to me:
(this line appears multiple times with recent tome and date)
I'll keep you updated, if I run into these errors again.

@github-actions[bot] commented on GitHub (Aug 31, 2023):
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.
@github-actions[bot] commented on GitHub (Sep 6, 2023):
Closing issue due to no activity in more than 60 days.