Skip to content

Conversation

@fedelibre
Copy link
Member

This fork re-enables MIDI output on macOS.
Fix #1946

@fedelibre
Copy link
Member Author

We have a problem with macOS signing

[frescobaldi] Notarizing DMG with team ID ***...

Submitting app for notarization... started
Submitting app for notarization... done

Briefcase will now wait for Apple to approve the notarization request.
This can take some time - in some cases, hours.

If notarization is interrupted, you can resume by running:

    briefcase package macOS app -p dmg --identity 7122EF914A5E99A9E7693F242E1865E964C48242 --resume 33b2cb95-7ef0-4cca-9d3f-343d22f5a02c

Waiting for notarization acceptance... started
Waiting for notarization acceptance... errored

Notarization was rejected: Archive contains critical validation errors

    * (error) Frescobaldi-4.0.3.dev1.dmg/Frescobaldi.app/Contents/MacOS/Frescobaldi [x86_64]
      The signature of the binary is invalid.
      https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735

    * (error) Frescobaldi-4.0.3.dev1.dmg/Frescobaldi.app/Contents/MacOS/Frescobaldi [arm64]
      The signature of the binary is invalid.
      https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735
Saving log... started

Log saved to /Users/runner/work/frescobaldi/frescobaldi/logs/briefcase.2025_06_03-09_26_18.package.log

Saving log... done
Error: Process completed with exit code 200.

@jacques-menu @davidfokkema Any help is appreciated.

fedelibre added a commit that referenced this pull request Jun 3, 2025
This fork re-enables MIDI output on macOS.
Fix #1946
@jacques-menu
Copy link
Collaborator

jacques-menu commented Jun 3, 2025 via email

@davidfokkema
Copy link

I'm trying to check on things locally. If I run briefcase package on my machine, I get the same error in the notarization step. I'll try out a few things.

@fedelibre
Copy link
Member Author

Thanks David, I can test only via GitHub Action. I've just added the following step to see if we get more information. I've launched now the workflow:

commit f1543912ca2a19e2782aa69edb3459e2c1070a3a (HEAD -> pygame-ce, origin/pygame-ce)
Author: Federico Bruni <[email protected]>
Date:   Tue Jun 3 12:42:30 2025 +0200

    Release workflow: add a command to debug macOS signing issues

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 90702cf0..7c93f9a7 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -127,6 +127,10 @@ jobs:
             ${{ matrix.briefcase-args }} \
             ${{ matrix.briefcase-package-args }}
 
+      - name: Debug macOS signing issues
+        if: ${{ failure() && (matrix.target == 'macOS') || (matrix.target == 'macOS-Intel') }}
+        run: pkgutil --check-signature dist/Frescobaldi-$VERSION.dmg
+
       # Briefcase generates Frescobaldi-$VERSION.dmg for
       # both macOS builds. We want to rename the Intel .dmg before
       # uploading it to Releases.

@davidfokkema
Copy link

Without local access the turnaround time is quite long. I just ran that command for example, and it complains it can only handle .pkg installer files and does not check .dmg disk image files or .app application bundles. I tried checking using codesign --verify but that keeps saying that all is well. I also just confirmed that the exact same version of briefcase still signs the master branch without problems, so I'll work my way up from there.

@davidfokkema
Copy link

The problem appears to be pygame-ce==2.5.4. I tried with pygame-ce==2.5.3 and that worked without problems. I'm trying both versions again, just to be sure, but each run takes about ten minutes.

@davidfokkema
Copy link

I can confirm that this seems to be correct and that even for a minimal Briefcase pygame app, this is the case: 2.5.4 fails, 2.5.3 works.

@fedelibre
Copy link
Member Author

Many thanks David! We'll stick to 2.5.3 until this is fixed upstream.

This fork re-enables MIDI output on macOS.
Fix #1946
Copy link
Collaborator

@bmjcode bmjcode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can confirm this works on Windows with 2.5.3. I'm good with merging this.

@fedelibre fedelibre merged commit 3495cb9 into master Jun 5, 2025
3 checks passed
@fedelibre fedelibre deleted the pygame-ce branch June 5, 2025 11:18
JunTamura1959 pushed a commit to JunTamura1959/frescobaldi that referenced this pull request Jun 7, 2025
This fork re-enables MIDI output on macOS.
Fix frescobaldi#1946
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MIDI output problem

5 participants