Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac: Notarization errors aren't shown #1862

Closed
cwensley opened this issue Jan 3, 2021 · 0 comments · Fixed by #2105
Closed

Mac: Notarization errors aren't shown #1862

cwensley opened this issue Jan 3, 2021 · 0 comments · Fixed by #2105
Milestone

Comments

@cwensley
Copy link
Member

cwensley commented Jan 3, 2021

Expected Behavior

When a notarization failure occurs, the errors should be shown in the build log so you know what to do. For example, when you need to sign contracts in the apple developer portal, etc.

Actual Behavior

The errors are hidden and it isn't apparent what the issue is. This is due to piping them through grep.

Steps to Reproduce the Problem

  1. Notarize a Mac app when contracts need signing

Specifications

  • Version: 2.5.8
  • Platform(s): Mac
  • Operating System(s): macOS (any)
@cwensley cwensley added this to the 2.5.x milestone Jan 3, 2021
cwensley added a commit to cwensley/Eto that referenced this issue Jan 3, 2022
- Build unified .app bundle from arm64 and x64 bundles.
- Create a single file when creating unified .app bundle by default as this is the only supported way currently.
- Report errors when notarization fails. Fixes picoe#1862
- Fix NUnit discovering tests when in single file bundle.
- Sdk will now create unified bundles by default for Mac
- Added SdkTest to test the sdk
- Updated monomac to fix issues running on ARM64 as it does not use stret methods for larger struct return values.
@cwensley cwensley modified the milestones: 2.6.x, 2.6.1 Apr 24, 2022
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 a pull request may close this issue.

1 participant