mirror of
https://github.com/Installomator/Installomator.git
synced 2026-03-08 03:22:12 +00:00
Broken app label: homebrew #132
Reference in New Issue
Block a user
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 @PhatAdam on GitHub.
All questions must be filled out or your Issue will be closed for lack of information
What's wrong with the app label?
Error verifying Homebrew.pkg
Have you confirmed this Issue has not been reported already? (Check open Issues and Pull requests)
yes, related issue was closed, i commented on it. I verified the AppID was correct 927JGANW46
Installomator version
What version are you running? You must include the version number and date. (Ex: Installomator v. 10.7beta, date 2024-08-31). **
10.7
74ac5514-days agoAdditional context
just attempted to install it, since i saw there was a new version and i have open tickets for it. Happy to test as needed.
Installomator log
At the bottom of this report, provide a log, either by running Installomator in Terminal and saving the output, or by downloading the result log from your MDM. Do not enable Debug logging level and please format the log using a code block!
[STEP 1 of 4]
Executing Policy Homebrew
[STEP 2 of 4]
Running script Installomator...
Script exit code: 4
Script result: 2025-01-28 15:34:29 : REQ : : shifting arguments for Jamf2025-01-28 15:34:29 : INFO : homebrew : Total items in argumentsArray: 0 2025-01-28 15:34:29 : INFO : homebrew : argumentsArray: 2025-01-28 15:34:29 : REQ : homebrew : ################## Start Installomator v. 10.8beta, date 2025-01-28 2025-01-28 15:34:30 : INFO : homebrew : ################## Version: 10.8beta 2025-01-28 15:34:30 : INFO : homebrew : ################## Date: 2025-01-28 2025-01-28 15:34:30 : INFO : homebrew : ################## homebrew 2025-01-28 15:34:30 : INFO : homebrew : SwiftDialog is not installed, clear cmd file var 2025-01-28 15:34:31 : INFO : homebrew : Reading arguments again: 2025-01-28 15:34:32 : INFO : homebrew : BLOCKING_PROCESS_ACTION=tell_user 2025-01-28 15:34:32 : INFO : homebrew : NOTIFY=success 2025-01-28 15:34:32 : INFO : homebrew : LOGGING=INFO 2025-01-28 15:34:32 : INFO : homebrew : LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns 2025-01-28 15:34:32 : INFO : homebrew : Label type: pkg 2025-01-28 15:34:32 : INFO : homebrew : archiveName: Homebrew.pkg 2025-01-28 15:34:32 : INFO : homebrew : no blocking processes defined, using Homebrew as default 2025-01-28 15:34:32 : INFO : homebrew : found packageID sh.brew.homebrew installed, version 4.4.9 2025-01-28 15:34:32 : INFO : homebrew : appversion: 4.4.9 2025-01-28 15:34:32 : INFO : homebrew : Latest version of Homebrew is 4.4.19 2025-01-28 15:34:32 : REQ : homebrew : Downloading https://github.com/Homebrew/brew/releases/download/4.4.19/Homebrew-4.4.19.pkg to Homebrew.pkg 2025-01-28 15:35:15 : INFO : homebrew : Downloaded Homebrew.pkg – Type is xar archive compressed TOC – SHA is b6c6230ad75cb53aeecb4f804c8420d6cac2376b – Size is 115500 kB 2025-01-28 15:35:15 : REQ : homebrew : no more blocking processes, continue with update 2025-01-28 15:35:15 : REQ : homebrew : Installing Homebrew 2025-01-28 15:35:15 : INFO : homebrew : Verifying: Homebrew.pkg 2025-01-28 15:35:16 : INFO : homebrew : Installomator did not close any apps, so no need to reopen any apps. 2025-01-28 15:35:16 : ERROR : homebrew : ERROR: Error verifying Homebrew.pkg error: Homebrew.pkg: rejected source=Unnotarized Developer ID origin=Developer ID Installer: Patrick Linnane (927JGANW46) 2025-01-28 15:35:16 : REQ : homebrew : ################## End Installomator, exit code 4
Error running script: return code was 4.
[STEP 3 of 4]
[STEP 4 of 4]
@acodega commented on GitHub:
Hi there, so Installomator does have an up-to-date label for homebrew, with Team ID 927JGANW46. I can not reproduce this issue and I'm able to install homebrew.
We do see verification fail on networks when proxying/filtering is in place. Can you reproduce this issue on a Mac on a "vanilla" network?
@5h4rk1337 commented on GitHub:
Maybe a issue with SSL Inspection?
https://support.apple.com/de-de/101555