About-This-Hack: App crashes in High Sierra

@0xCUB3 @MDNich @nocontent06 @yanisalbert @Matgen84 @perez987 Hi I made a mistake, issue N78 “scr.txt” Display section has a " Built-In " with I uppercase. There’s no reliable rule

So the code must be as follow grep " " /…/…/scr.txt | egrep “Built-[I|i]n”

~/0ATH/Data Tests/0-ath-issue-N78/scr.txt: Display Type: Built-In Retina LCD ~/Data Tests/0-ath-issue-N99/scr.txt: Display Type: Built-in Liquid Retina XDR Display

The new one https://drive.google.com/file/d/19eqr3DtVdbr4HhjOUu3QX_UUJFucda9T/view?usp=sharing

Tests mad with issues N39, N72, N72bis, N78, and N99 DataFiles and the result is the same apart with my Laptop

I’ll build this new version on Monterey with Xcode 14,2 to test it on High Sierra

0xCUB3 tell me if I must push latest modifications (since last PR not yet integrated)

I’m tired, and busy next week.

Regards

@0xCUB3 @baguswaber @5T33Z0 @perez987

Hi all

ATH works (fine … baguswaber would confirm that) with High Sierra 10.13.6 on an External HDD with High SIerra 10.13.6 it works, Tooltips too, as you can see below, I didn’t test upgrade (coz’ latest version available is 0.9.1 (version returned from github in version.txt) and version of this ATH Appli (G0R0C0) is 1.0.0

with ToolTips No Upgrade available Progress bar stays grey (or empty)

Just an inconvenience, the grey (not) colored progress bar (and no ToolTip on (… External USB)…) on HDD picture ToolTip is OK

Appli (on Google Drive) https://drive.google.com/file/d/19oNxPOvLaS1GYe96tqrpftM0NzLxE9Iw/view?usp=drive_link

Regards

@0xCUB3 @MDNich @nocontent06 @yanisalbert @Matgen84 @perez987

Hi

clamshell mode : you treat your laptop like a desktop tower, disabling the laptop’s built-in screen…

Yes but if you search in your “/tmp/.ath/scr.txt” the string “Built-In” what do you see

And I realize that the way to determine a “Built-In display” is a wrong way

static func hasBuiltInDisplay() -> Bool {
    let tmp = run("grep \"Built-In\" " + initGlobVar.scrFilePath + " | tr -d '\n'")
    return !(tmp == "")
}

What is returned is the GPU status ( Bus: Built-In ) not the display one (Built-in). GPU “Built-In” with I "-In"uppercase (search criteria in code (was never modified)), Display “Built-in” has a I lowercase.

Here is the “scr.txt” you send for test Graphics/Displays:

Apple M2 Pro:

  Chipset Model: Apple M2 Pro
  Type: GPU
  Bus: Built-In
  Total Number of Cores: 19
  Vendor: Apple (0x106b)
  Metal Support: Metal 3
  Displays:
    Color LCD:
      Display Type: Built-in Liquid Retina XDR Display
      Resolution: 3024 x 1964 Retina
      Main Display: Yes
      Mirror: Off
      Online: Yes
      Automatically Adjust Brightness: Yes
      Connection Type: Internal

If I search in all issues “scr.txt”

Issue N39 “scr.txt” it’s a GPU Built-in egrep “Built-[I|i]n” ~/“0ATH/Data Tests”/0-ath-issue-N39/scr.txt Bus: Built-In

Issue N72 an N72bis distinct “scr.txt” without GPU Built-In nor Display Built-in egrep “Built-[I|i]n” ~/“0ATH/Data Tests”/0-ath-issue-N72/scr.txt egrep “Built-[I|i]n” ~/“0ATH/Data Tests”/0-ath-issue-N72bis/scr.txt

Issue N78 “scr.txt” both GPU Built-In and Display Built-in egrep “Built-[I|i]n” ~/“0ATH/Data Tests”/0-ath-issue-N78/scr.txt
Bus: Built-In Display Type: Built-In Retina LCD

Issue N99 (yours 0xCUB3) “scr.txt” both GPU Built-In and Display Built-in egrep “Built-[I|i]n” ~/“0ATH/Data Tests”/0-ath-issue-N99/scr.txt Bus: Built-In Display Type: Built-in Liquid Retina XDR Display

So the search criteria must be “Built-in” with I (-in) lowercase.

Previous one is with “Built-In” with I (-In) uppercase.

And this one below is with “Built-in” with I (-in) lowercase. https://drive.google.com/file/d/1OgT_J8EiKV_7-Ekj6QDcrhOj5SHsN4h8/view?usp=sharing And the result on my Laptop is different : from “Unknown Display” to a simple “Display”, my Laptop display is not considered as a “Built-in” Display (there’s no “Built-in” in /tmp/scr.txt Display section)

From To

Regards

@0xCUB3 @MDNich @nocontent06 @yanisalbert @Matgen84 @perez987

Hi Finally I thought it was a problem with EN storyboard, so I deactivate (remove reference) FR storyboard from Project to have only EN language, but unfortunately it’s not the reason why. I build and test it with all issues DataFiles even yours 0xCUB3 and all builds with EN and FR storyboards show a Display(s) name(s) in Displays Tab. All tests mad on my Laptop Ivy Bridge (Graphic and Broadcom Patched with OCLP, not sure Xcode doesn’t like it) on Ventura and Xcode 15.0.1 builds. Xcode 15.x problem, Swift 5 problem ? If somebody knows …

0xCub3

Below the last version you’ve tried (with EN storyboard)

Below the new build (tested with only EN storyboard to show you the result)

Result is the same

Last ATH build (and I push modifications in my Github Repo and open a PR) build with EN and FR storyboard activated. WITH $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/macosx/libswiftAppKit.dylib in project “build setting/Other Linker Flags”

https://drive.google.com/file/d/1S4GX9iJ86uLi_1vNbsck8Ihpo1YzLoDC/view?usp=drive_link

I push on Google Drive another build from which i removed the Compatibility Flag for High Sierra WITHOUT $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/macosx/libswiftAppKit.dylib in project “build setting/Other Linker Flags”

If this one works fine it’ll be a problem with TOOLCHAIN (Xcode or User one) https://drive.google.com/file/d/1Ls83h2K3xPBl8YWCHpxn7ACzjTqYE_Ag/view?usp=drive_link

Regards

I’ve fixed that Clover pproblem with Old Clover Rev.

Built with Xcode 14.2 and tested on Ventura, Monterey and High Sierra

I can’t (network or github can’t) upload screenshots of High Sierra, Monterey and Ventura.

And if you ask me a GO I answer you “you can GO”

The same build Xcode14.2 is used with this three macOS

@matxpa do you feel ready for a 1.0.0 release??? I think I am 😃

idk what the issue there is. Nothing on my end. Could you troubleshoot? Maybe the older version of zsh doesn’t support our commands? idk

Try this one made with Xcode 12: https://drive.google.com/file/d/1Yq_M2M6xOI0SOXwh1JlagsrzdC6XGxk0/view?usp=sharing

@0xCUB3

Hi

Built with Monterey 12.6.6 and Xcode 14.2 and Deployment Target 10.11 In ATH appli info.plist : BuildMachineOSBuild = 21G646 --> Monterey 12.6.6 (21G646) DTXcode = 1420 --> Xcode 14.2 LSMinimumSystemVersion = 10.11 --> El Capitan

In ATH Project (TARGETS/Build Settings/macOS Deployment Target) LSMinimumSystemVersion MACOSX_DEPLOYMENT_TARGET = 10.11;

And if you try to build ATH with Ventura, Xcode 15.0 (15A240d) and TARGETS/Build Settings/macOS Deployment Target = 10.11

The macOS deployment target ‘MACOSX_DEPLOYMENT_TARGET’ is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.0.99. (and what could happen with Sonoma 14.1 beta ???)

So we could try with LSMinimumSystemVersion at 10.12 or 10.13 but imperatively with Xcode 14.2 (Monterey 12.5 mini) Xcode 14.3, 14.3.1 and newer work only with Ventura (13.3 mini) and Sonoma

Regards

@0xCUB3 @perez987 Hi I’ve made changes in UpdateController.swift … static func updateATH() { … // let rm = run(“rm -rf "” + initGlobVar.thisAppliLocation + “"”) let rm = run(“rm -rf "(initGlobVar.thisAppliLocation)"”) … // _ = run(“[[ ! -d "” + initGlobVar.thisAppliLocation + “" ]]”) _ = run(“[[ ! -d "(initGlobVar.thisAppliLocation)" ]]”) … // _ = run("cp -rf " + initGlobVar.athDirectory + “"” + initGlobVar.thisAppliname + “" " + initGlobVar.allAppliLocation) _ = run(“mv -f (initGlobVar.athDirectory)” + “"(initGlobVar.thisAppliname)"” + " (initGlobVar.allAppliLocation)”) … // _ = run("open " + initGlobVar.allAppliLocation + “"” + initGlobVar.thisAppliname + “"”) _ = run(“open "(initGlobVar.thisAppliLocation)"”) …

New build App (today) placed in /Application with a ShortVersionString downgraded

Now the upgraded ATH App from 0.9.0 to 0.9.1 (20230728) and immediately opened

And the Upgrade works fine (tested with Monterey and Xcode 14.2 (14C18) (since few days my Ventura platform is unstable)

I made also changes on both Main.storyboard (IN MY REPO) but don’t apply that, coz’ Storage Name & Info Displayed on Storage Tab are different between our two Repo.

Below is before changes

Below is after changes

And below Storage Tab from your Repo

All of those changes had been pushed in github matxpa ATH repo (branch main)

Regards

@0xCUB3 @perez987

upgrade doesn’t work for that reason : Last Release ID retrieved (in .ath/version.txt) is 1.0.0, but https://github.com/0xCUB3/About-This- Hack/releases/download/1.0.0/About.This.Hack.zip doesn’t exist.

Some adjustments/corrections made too in InitGlobalVariables.swift and UpdateController.swift. But I can’t test this upgrade, may be if you change the content of the file which contains Last Release ID (aka to 0.9.1) and I change in my local PROJECT Version from 0.9.9 to 0.8.9 I could test upgrade

Application https://drive.google.com/file/d/18OvgIAE1xggqsXsHaJQ_lJSPgQVAiVkQ/view?usp=sharing

Source https://drive.google.com/file/d/1EWY0KQM1TwEjjJHo8bYWY6bLXMnjSxq2/view?usp=sharing

And I update my fork, i’ll send you a message when it will be ok

Regards

I think the underlying issue is that I am using Xcode 16 beta, which can only build for macOS Big Sur and newer (I believe)… I’ll have to figure out a workaround. @baguswaber please stay tuned.