Jump to content
70 posts in this topic

Recommended Posts

https://swdist.apple.com/content/downloads/08/22/140-31668-A_UOOEA5WMR8/yx13s8l4tygi9n1ar7rxhrhpn9t04wvk1n/InstallAssistant.pkg

 

        <dict>

            <key>BUILD</key>

            <string>26A5368g</string>

            <key>VERSION</key>

            <string>27.0</string>

 

[ 35 ] 2026-06-22 17:16:36 .. 140-31668 .. 27.0.0.26A5368g macOS Golden Gate Beta

  • Like 2

This time a sequential OTA update of just 10 GB!  

 

image.thumb.png.a2da437e161b810ed66e01499b02bebb.png

 

image.thumb.jpeg.a09fc90359e69c6bdad6cbe24019dc07.jpeg

 

With macOS 27 beta 2 (26A5368g), Apple appears to have fixed the following issues on my MacBook Pro M1:

  1. Keyboard and trackpad now work immediately after waking from sleep or opening the lid.
  2. No Wi-Fi issues after waking from sleep or opening the lid.
  3. Secondary click now works perfectly when configured as "Click in Bottom Right Corner".

Interestingly, Apple released Kernel Debug Kit macOS 26.7 build 26A5368g, apparently confusing macOS 27 beta 2 with macOS 26.7. :hysterical:

 

image.thumb.png.3c2d6d06b7dfce04ceead5fc2820f052.png

 

 The very bad part of this funny confusion at first glance:

 

Any future Tahoe 26.7 KDK release is unlikely to carry a build number higher than 26A. Consequently, Kernel Debug Kit macOS 26.7 build 26A5368g - which actually belongs to macOS 27 beta 2 (Golden Gate) — would not be compatible with macOS Tahoe.

 

If Apple keeps this naming scheme, OCLP's automatic KDK matching could become problematic beyond macOS Tahoe 26.6, as it may no longer be possible to reliably distinguish Tahoe 26.7 KDKs from Golden Gate KDKs based on build numbering alone. This assumes, of course, that macOS 26.7 will be the final major Tahoe release. 🤕

 

Whether this is an actual mistake or an intentional change in Apple's KDK naming scheme remains unclear. If intentional, OCLP and similar tools may eventually need to adjust their KDK matching logic accordingly.

 

I have already submitted a Feedback Assistant report to Apple regarding this apparent KDK naming issue.

Edited by kgp
  • Like 2
  • 2 weeks later...

@kgp

I already mentioned to @fantomas that Golden Gate is clearly more demanding than Tahoe with Gatekeeper, but until now Xattr-remove (sometimes requiring you to select "Re-sign app") or Sentinel (signing the app or disabling Gatekeeper) solved this issue.

 

I'm worried after reading you that Apple has further tightened this system because then... what will we do with all the free, open-source apps that aren't notarized? What a problem!

 

However, I see that @surenmunoo has uploaded a screenshot of ATH with GG beta 3.

 

I haven't downloaded beta 3 yet; I'll do it later and comment.

  • Like 2

@kgp

Indeed, xattr quarantine removal is not enough to run the app, but re-signing app and Sparkle does the job. Checking re-sing the app in Xattr-remove, I am able to run ATH as expected. This does the same as code signing Sparkle and app in your own machine:

codesign --force --deep --sign - \
  About\ This\ Hack-glass.app/Contents/Frameworks/Sparkle.framework

codesign --force --deep --sign - \
  About\ This\ Hack-glass.app

I suppose that you must have at least one Apple account in Xcode settings or in the Keychain to this task to work.

 

Spoiler

 

Xattr-remove.thumb.png.e8021d864915ae8c2b4c87a41cb2cd5a.png

 

 

Edited by miliuco
Typo
  • Like 1

 

Hello my dear friends, 

@miliuco

I used VS Code with Copilot to compile About This Hack with Xcode because I prefer the hidden serial number to open as a native option. I only had to grant permission in Sentinel and didn’t need to sign the application. It opened normally on Golden Gate Beta 3.

Regards ;) 

 

image.png.3d190184655f46bd3c6f0a0e379d5097.png

  • Like 1
1 hour ago, miliuco said:

@kgp

Indeed, xattr quarantine removal is not enough to run the app, but re-signing app and Sparkle does the job. Checking re-sing the app in Xattr-remove, I am able to run ATH as expected. This does the same as code signing Sparkle and app in your own machine:

codesign --force --deep --sign - \
  About\ This\ Hack-glass.app/Contents/Frameworks/Sparkle.framework

codesign --force --deep --sign - \
  About\ This\ Hack-glass.app

I suppose that you must have at least one Apple account in Xcode settings or in the Keychain to this task to work.

 

  Reveal hidden contents

 

Xattr-remove.thumb.png.e8021d864915ae8c2b4c87a41cb2cd5a.png

 

 

 

@miliuco, many thanks for your immediate feedback! 🤗

 

First, one observation I already observed quite a while ago: when downloading About.This.Hack-4.3.9-glass.zip. the included app is also named  About\ This\ Hack.app and no longer  About\ This\ Hack-glass.app. Nevertheless, the included version is definitely the glass version. 

 

What worked for me after downloading the app:

 

1.)  

codesign --force --deep --sign - \
  About\ This\ Hack.app/Contents/Frameworks/Sparkle.framework

codesign --force --deep --sign - \
  About\ This\ Hack.app

2.) Subsequently dropping the app into the Sentinel.app or Xattr-remove.app

 

This solved my issue with the app under macOS 27 beta 3.

 

image.thumb.jpeg.13b6519649ed68cad5ae5b7c23317f1c.jpeg

 

The same approach also worked for Download Full Installer 4.5.3:

 

image.thumb.png.fd50769aebe19c2fbb1eae8428877aab.png

 

Edited by kgp
  • Like 3
×
×
  • Create New...