About This Hack (2009-Nissan-Cube version migrated to SwiftUI)

[miliuco]

@kgp

 

Sandbox is the preferred way of secure user files in macOS. Since ATH was always unsandboxed, I keep it so. But when I try the notarized app, I find that, without sandbox, there are issues, maybe notarization works better with sandbox although I’ve read that it’s not mandatory that both go together. 
Think that I’m going into notarization for the first time and I’m still a rookie, a lot of things to learn in the past 3 days and I have to learn a lot more. 
E.g. I don’t like the DMG type over ZIP for releases but ZIP is giving to me translocation errors when checking for updates, DMG doesn’t.

It’s a work in progress, maybe I’ll make changes, current state of the project is not definitive. 
Anyway, thanks to all for your help, I’ll need it to improve ATH. 
 

@kaoskinkae

Do you mean the custom logo? Do you see poor quality in it?

The logo previously set disappears because sandbox changes the localization of the app user files, now in ~/Library/Containers, set the logo again and tell me what happens. I’ll try it on my side and comment. 
But logo quality must be the same, I’ll try it too. 

[kaoskinkae]

Just now, miliuco said:

@kgp

 

Sandbox es la forma preferida de proteger los archivos de usuario en macOS. Como ATH siempre estuvo sin sandbox, lo mantengo así. Pero cuando pruebo la aplicación notarizada, encuentro que, sin sandbox, hay problemas, tal vez la notarización funcione mejor con sandbox aunque he leído que no es obligatorio que ambos vayan juntos. 
Piensen que estoy entrando en la notarización por primera vez y todavía soy un novato, hay mucho que aprender en los últimos 3 días y tengo que aprender mucho más. 
Por ejemplo, no me gusta el tipo DMG sobre ZIP para las versiones, pero ZIP me da errores de translocación al buscar actualizaciones, DMG no.

Es un proyecto en desarrollo, tal vez haga cambios; su estado actual no es definitivo. 
De todos modos, gracias a todos por su ayuda, la necesitaré para mejorar ATH. 
 

@kaoskinkae

¿Te refieres al logotipo personalizado? ¿Notas que tiene mala calidad?

El logo que habíamos configurado previamente desaparece porque el entorno aislado modifica la localización de los archivos de usuario de la aplicación, que ahora se encuentran en ~/Library/Containers. Vuelve a configurar el logo y dime qué ocurre. Lo probaré y te comentaré. 
La calidad del logo debe ser la misma, así que también lo probaré. 

This happened to me the other day, but I didn't think much of it. I just noticed, though, that once you change the logo, close and reopen the application, the custom logo disappears and the generic one appears, depending on your Mac system (in my case, Tahoe). I'm not sure if the quality could be improved, even if you hover over the "view larger" option.

[miliuco]

@kaoskinkae

Logo quality is good for me but you are right, custom logo not saved between re-runs.

Something I've changed in past days has changed this (sandbox most probably), I have to check where the issue is.

 

 

[miliuco]

@kaoskinkae

 

Custom logo persistence fixed. The logo is saved in user default folder and deleted if logo reset to default or replaced with another logo. Please try and comment.

 

https://github.com/perez987/About-This-Hack/releases/tag/4.4.6

[kaoskinkae]

1 hour ago, miliuco said:

@kaoskinkae

 

Custom logo persistence fixed. The logo is saved in user default folder and deleted if logo reset to default or replaced with another logo. Please try and comment.

 

https://github.com/perez987/About-This-Hack/releases/tag/4.4.6

perfect 

 

[kgp]

@miliuco, About This Hack 4.4.7 (zip version instead of dmg) works perfectly fine under both macOS 26.5.2 and macOS 27 beta 3! 😜  

 

 

 

Edited 14 hours ago by kgp

[miliuco]

@kgp

You're getting ahead of yourself 😂

 

This release 4.4.7 is just to test if the update from 4.4.6 works fine; there were no code changes whatsoever.

After seeing that it works fine, I removed it. As I said, the code is the same as in 4.4.6.

 

Thank you so much for all the information you've given me from the beginning.

[Max.1974]

Thanks to the DEVS!!  

 

[miliuco]

@Max.1974

 

Startup disk name is empty. Please show to me the system disk tab, on the same machine and macOS of these pics.

[Alpha22]

  

[miliuco]

@Alpha22

 

You too, startup disk name empty. Both are running Ventura, though I'm not sure if that's related. Do you have a different macOS version on the same machine to see if the same thing happens?

 

@kgp  @kaoskinkae  myself have the startup disk name filled. But you and @Max.1974 don't.

 

These issues are difficult to debug remotely.
If you or @Max.1974 can test the Xcode project (on macOS Ventura), show to me the console messages, in case there is something useful.
Thank you.

 

Edited 53 minutes ago by miliuco
Typo

[Alpha22]

9 minutes ago, miliuco said:

You too, startup disk name empty. Both are running Ventura, though I'm not sure if that's related. Do you have a different macOS version on the same machine to see if the same thing happens?

No problems with macOS Thaoe, i’ll check on macOS Sequoia

[Alpha22]

No problems with macOS Sequoia

 

[miliuco]

@Alpha22

Thanks, the issue seems to be focused on Ventura.

I'll wait for @Max.1974 testing the Xcode project in Ventura, currently I don't have Ventura but in the meantime I can try Sonoma.