Post

Replies

Boosts

Views

Activity

Reply to What is the reliable approach to fetch a consistent and complete list of installed applications?
Recommended, preferred and reliable?! That's a tall order! 😅 I can offer a few method, mdfind is super fast, it uses the content type names and values you can get with mdls <app path> This one gets all application types, including .service files, the kMDItemContentTypeTree has a multiple of types in it mdfind 'kMDItemContentTypeTree == com.apple.application' This one doesn't include .service files since it uses the kMDItemContentType which can only have one value: mdfind 'kMDItemContentType == com.apple.application-bundle' Lastly (and the most slow), would be system_profiler. This one-liner assumed the Mac is macOS Tahoe which ships with jq: system_profiler -json SPApplicationsDataType | jq -Mr '.. | .path? // empty' Oh and this is UI only and doesn't export a list (although there probably is a way) but you can paste this in Script Editor to get a list of apps (that is considerably shorter than the other methods): choose application with prompt "Pick an app:"
2w
Reply to "Provisioning profile does not allow this device" on Sequoia 15.2 VM
I suppose I'll be filing feedback on behalf of our developers at work also. We were pretty surprised to see the Provisioning UDID be rejected in the Apple Developer portal when we tried to add a macOS device, it simply replies with: The following devices are either already present and were not modified or contain invalid identifiers. So it seems macOS Sequoia VMs cannot use development provisioning profiles because they cannot be added as a Device in the Developer portal
Mar ’25
Reply to What is the reliable approach to fetch a consistent and complete list of installed applications?
Recommended, preferred and reliable?! That's a tall order! 😅 I can offer a few method, mdfind is super fast, it uses the content type names and values you can get with mdls <app path> This one gets all application types, including .service files, the kMDItemContentTypeTree has a multiple of types in it mdfind 'kMDItemContentTypeTree == com.apple.application' This one doesn't include .service files since it uses the kMDItemContentType which can only have one value: mdfind 'kMDItemContentType == com.apple.application-bundle' Lastly (and the most slow), would be system_profiler. This one-liner assumed the Mac is macOS Tahoe which ships with jq: system_profiler -json SPApplicationsDataType | jq -Mr '.. | .path? // empty' Oh and this is UI only and doesn't export a list (although there probably is a way) but you can paste this in Script Editor to get a list of apps (that is considerably shorter than the other methods): choose application with prompt "Pick an app:"
Replies
Boosts
Views
Activity
2w
Reply to "Provisioning profile does not allow this device" on Sequoia 15.2 VM
I suppose I'll be filing feedback on behalf of our developers at work also. We were pretty surprised to see the Provisioning UDID be rejected in the Apple Developer portal when we tried to add a macOS device, it simply replies with: The following devices are either already present and were not modified or contain invalid identifiers. So it seems macOS Sequoia VMs cannot use development provisioning profiles because they cannot be added as a Device in the Developer portal
Replies
Boosts
Views
Activity
Mar ’25