Fixing Launch Services Problems
When a document is set to be opened by an app other than the default for its UTI, a com.apple.LaunchServices.OpenWith extended attribute is added, containing a property list specifying[…]
[…]
When an app is first run from the Finder and GUI, information about it is extracted from its Info.plist file and added to LaunchServices’ database. This includes custom document types specified by the app and its abilities to open and edit different types of document. These are then used to match document UTIs against the apps that can open them. Unless you’ve set any different, LaunchServices should normally open the most recent version of the specified app in your Applications folder[…]
[…]
There are two command tools that can be valuable for tackling harder problems:
lsappinfofor getting information from LaunchServices’ database, andlsregisterfor changing it.
Previously:
- Rebuilding the Launch Services Database
- LaunchCodes 1.0
- Creator Codes and UTIs
- Creator Codes in Snow Leopard
- Bruce Horn Interview
