Mac OS App Releases 3.2.0 and 3.4.0 fail to execute - missing dependencies.

[scottfurry]

Platform: Mac Mini (late 2018)
OS: Sequoia 15.5
Install Method: manual using available "full" dmg files

Last working version encountered was PySolFC-3.1.0. Attempted upgrade to PySolFC-3.4.0_full but encountered py2app error dialog.

Uninstalled PySolFC app, including component directories, and attempted re-install. No Change.

Repeated uninstall steps, downloaded and installed PySolFC-3.2.0_full where I encountered same problem.

Verified sha1 checksums were correct for all downloads. Repeated uninstall steps and reverted to PySolFC-3.1.0 install.

Obtained a copy of DirEqual app and compared app contents for 3.4.0 and 3.2.0 against 3.1.0.

Comparison revealed that PySolFC app builds for last two releases (3.4.0 and 3.2.0) were incomplete and missing crucial library dependencies needed for execution. (see images)

DirEqual compare 3.1.0 -> 3.2.0

DirEqual compare 3.1.0 -> 3.4.0

Change to build process would have been made before 3.2.0 release. Unable to identify changed file responsible for problems observed.

Will attempt to build locally to identify problem.

[scottfurry]

Cobbled together a process to build locally. While the process completed successfully, a viable app could still not be produced. Executing the resultant app still produced a py2app error dialog stating a launch failure occurred.

Output of build was redirected to a text file for review. Multiple warnings were encountered but there were no outright indications of build step failure in the output. Some warnings were deprecation advisories and suggest a cleanup and/or refactoring may be necessary going forward.

For completeness, steps utilized to produce app locally are provided here:
(edit:document corrections)

macos_setup_steps.txt

[joeraz]

Based on my limited understanding, if the Mac builds broke, this commit is likely the reason: 4566cb2

Right before the 3.2.0 release, the Mac builds did not run as macos-12 was no longer an option, so I was forced to update it to macos-14. Sadly, with no Mac test environment of my own, I have no way to verify anything with the mac releases. I've been able to update libraries without issue, but even trying to update to the newer versions of Python broke it at one point.

Can a variant of that script be used in https://github.com/shlomif/PySolFC/blob/master/.github/workflows/macos-package.yml to fix the package?

[scottfurry]

On 2025-07-12 21:08, Joe R. wrote: Based on my limited understanding, if the Mac builds broke, this commit is likely the reason: 4566cb2 <https://github.com/shlomif/PySolFC/ commit/4566cb2fc55eeea3fa4655f3834a8d13f3bbf90e>

I'll walk through that commit to verify matters. It could also be something external, such as a py2app update or similar. Too many variables involved here.

Right before the 3.2.0 release, the Mac builds did not run as macos-12 was no longer an option, so I was forced to update it to macos-14. Sadly, with no Mac test environment of my own, I have no way to verify anything with the mac releases. I've been able to update libraries without issue, but even trying to update to the newer versions of Python broke it at one point.

One thing I haven't tried is to build a standalone python application, as in run it as python but not necessarily encapsulated as an app. That my shake out some problems along the way.

Can a variant of that script be used in https://github.com/shlomif/ PySolFC/blob/master/.github/workflows/macos-package.yml <https:// github.com/shlomif/PySolFC/blob/master/.github/workflows/macos- package.yml> to fix the package?

In my reply to the original message, I included a text file of the steps I followed in attempting to construct the app. It's largely based on the github macosx workflow file. The process, overall, appears reasonable. I want to believe that a tweak of settings would be needed to correct some upstream change. Some salient detail were missing, or glossing over, is causing grief. One last thing I should point out is the residuals that exist in the source tree. One Ex. is what looks like a partial download committed to the full cardset tree - a hidden file starting w/ '.'. There are other files in the sources that directly reference v2.x that seem like leftovers from past efforts. A good source tree scrub would seem prudent and my strong recommendation.

[scottfurry]

Item not forgotten.
Currently trying to resolve ttktheme install issue - TkinterEP/ttkthemes#97

[scottfurry]

Some forward momentum. Dev's at TkinterEP/ttkthemes were able to isolate problem with install of package. The recent changes to python infrastructure, and struggle to keep up, appears to be the cause of some problems.

With the dependencies installable, focus is now on building the PySolFC itself.