Apple has run the death bell on 32-bit macOS apps and, if you’re running a recent macOS version on your Mac (which you should so you can get security updates) you likely see this alert from time-to-time:
If you’re like me, you click through that and keep working but later ponder just how many of those apps you have. They are definitely going away, so knowing if your favourite app is on the chopping block is likely a good idea.
You can get this information via the “About This Mac”͢”System Report” app and sorting via one of the table fields.
R folks are data folks and we know we can do better than that. But, first we need to get the data. Thankfully, we can get this via the system_profiler command-line utility since it can both display user-friendly information in the terminal and also generate an XML version of the information to work with. We won’t need to head to the terminal for this work, though, since there are many ways to execute the command from R and read the generated output.
Executing System Calls from R
Base R provides two core methods for issuing a system call:
Note that there are other functions provided with a base R installation that can also issue system commands and process the “piped” output, but we’ll focus on these deliberate invocation ones.
Functions in two other packages can also assist with this task and we’ll include a look at:
processx::run()sys::exec_internal()
as well.
Why leave base R for this task? Truthfully, we really don’t need to, but both sys and processx have other tasks which do make them handy tools in your package toolbox. Having said that, keep reading since we’re going to end up not choosing the built-in functions for this task.
This is the command line we need to execute:
system_profiler -xml -detailLevel full SPApplicationsDataType
Let’s load up all the packages we’ll be needing and execute this command-line all four ways, then briefly discuss the differences:
library(sys)
library(processx)
library(microbenchmark)
library(xml2)
library(tidyverse)
system(
command = "system_profiler -xml -detailLevel full SPApplicationsDataType",
intern = TRUE
) -> apps_system
str(apps_system)
## chr [1:10665] "" ...
system2(
command = "system_profiler",
args = c("-xml", "-detailLevel", "full", "SPApplicationsDataType"),
stdout = TRUE
) -> apps_system2
str(apps_system2)
## chr [1:10665] "" ...
processx::run(
command = "system_profiler",
args = c("-xml", "-detailLevel", "full", "SPApplicationsDataType"),
spinner = TRUE
) -> apps_processx_run
str(apps_processx_run)
## List of 4
## $ status : int 0
## $ stdout : chr "XML STRING THAT prism.js won't let me show"
## $ stderr : chr ""
## $ timeout: logi FALSE
sys::exec_internal(
cmd = "system_profiler",
args = c("-xml", "-detailLevel", "full", "SPApplicationsDataType")
) -> apps_sys_exec_internal
str(apps_sys_exec_internal)
## List of 3
## $ status: int 0
## $ stdout: raw [1:331133] 3c 3f 78 6d ...
## $ stderr: raw(0)
The core difference between system() and the rest is that you need to shQuote()? for system() whereas that’s taken care of for you by the others (so they’re a bit safer by default since you’re more than likely going to forget to shQuote()).
You can definitely notice the main differences in return objects. The built-in functions just give us the character data from the standard output stream (stdout) and the last two return a more structured object that provides more explicit information about the job we just executed. The base ones can provide this detail, but it’s a twisty maze of remembering which options do what vs the more (IMO) straightforward approach both processx and sys take.
You’ll also notice a difference in stdout between processx and sys with the latter giving us a raw vector vs a character vector. This gives us a great deal of power and flexibility. It also turns out to be a great choice for processing command-line-generated XML data. Here’s why:
microbenchmark(
sys = xml2::read_xml(apps_sys_exec_internal$stdout),
processx = xml2::read_xml(apps_processx_run$stdout)
)
## Unit: milliseconds
## expr min lq mean median uq max neval
## sys 4.086492 4.60078 9.085143 5.508814 5.906942 207.6495 100
## processx 9.510356 10.98282 14.275499 12.054810 13.292234 163.9870 100
It turns out xml2::read_xml() makes much quicker work of the raw vector data (though, I mean, really—are we really going to care about those ~5ms IRL?).
We’ll move on to the real reason for the post, but definitely explore both sys and processx since they are both super-handy packages.
“Can we please just find the 32-bit apps already?”
No problem. Well, actually, there is a minor annoyance. These are property list XML files and I’ll confess that I truly hate this format. There are “dictionary arrays” of key and value nodes, but those nodes are siblings vs directly associated pairs. So, we have to use the sibling relationship to work with them. It’s not hard, per se, just (again, IMO) suboptimal.
Let’s take a look at it:
apps <- read_xml(apps_sys_exec_internal$stdout)
xml_find_all(apps, "//array/dict")
## {xml_nodeset (476)}
## [1] \n _SPCommandLineArguments\n \n ...
## [2] \n _name\n Sublime Text\n h ...
## [3] \n _name\n System Preferences\n ...
## [4] \n _name\n Google Chrome Canary\n ...
## [5] \n _name\n Google Chrome\n ...
## [6] \n _name\n Dropbox\n has64B ...
## [7] \n _name\n Keypad\n has64Bi ...
## [8] \n _name\n Garmin WebUpdater\n < ...
## [9] \n _name\n LaTeXiT\n has64B ...
## [10] \n _name\n CocoaPacketAnalyzer\n ...
## [11] \n _name\n Janetter\n has64 ...
## [12] \n _name\n VMware Fusion\n ...
## [13] \n _name\n Photo Library Migration Utility ...
## [14] \n _name\n Setup Assistant\n \n _name\n Siri\n has64BitI ...
## [16] \n _name\n Software Update\n \n _name\n Spotlight\n has6 ...
## [18] \n _name\n Stocks\n has64Bi ...
## [19] \n _name\n SystemUIServer\n \n _name\n UniversalAccessControl ...
## ...
Let’s look at a sample record using xml_view() from the htmltidy package:
xml_find_all(apps, "//array/dict[key='_name']")[1] %>%
htmltidy::xml_view()
Be wary of using xml_view() on giant XML structures since it’ll freeze up RStudio for a bit and even slows down Chrome since the resultant, composed DOM object can get ginormous.
Now we know we can use has64BitIntelCode for filtering once we get to the data. Let’s read in all the apps, cherry-picking the fields and then just look at the 32-bit apps:
xml_find_all(apps, "//array/dict[key='_name']") %>%
map_df(~{
list(
name = xml_find_first(.x, ".//string") %>% xml_text(),
path = xml_find_first(.x, ".//key[.='path']/following-sibling::string") %>% xml_text(),
is_64bit = xml_find_first(.x, ".//key[.='has64BitIntelCode']/following-sibling::string") %>% xml_text()
)
}) %>%
filter(is_64bit == "no") %>%
arrange(name) %>%
select(-is_64bit)
## # A tibble: 30 x 2
## name path
##
## 1 AAM Registration Notifier /Applications/Utilities/Adobe Application Mana…
## 2 AAM Registration Notifier /Applications/Utilities/Adobe Application Mana…
## 3 AAM Updates Notifier /Applications/Utilities/Adobe Application Mana…
## 4 AAMLauncherUtil /Applications/Utilities/Adobe Application Mana…
## 5 ACR_9_10 /Library/Application Support/Adobe/Uninstall/A…
## 6 Adobe Application Manager /Applications/Utilities/Adobe Application Mana…
## 7 adobe_licutil /Applications/Utilities/Adobe Application Mana…
## 8 Audacity /Applications/Audacity.app
## 9 COCM_1_0_32 /Library/Application Support/Adobe/Uninstall/C…
## 10 COPS_1_0_32 /Library/Application Support/Adobe/Uninstall/C…
## # ... with 20 more rows
The Adobe helper apps are longstanding 32-bit “offenders”. Many of these death-row apps fall into the “helper” category and will hopefully get some attention by their developers. I do find it amusing that Apple kinda wants us to prod the developers to get their collective acts together.
FIN
This exhaustive search finds all of the 32-bit apps residing on your system. If you just want to see the one’s you’ve executed and macOS has kept track of, you can drop to a command-line and do:
sudo Rscript -e 'knitr::kable((dplyr::select(dplyr::tbl(dplyr::src_sqlite("/var/db/SystemPolicyConfiguration/ExecPolicy"), "legacy_exec_history_v3"), responsible_path)))'
You need elevated privileges to access those files, so please read that whole line to make sure I’m not having you rm -rf /.
Remember to take some time to explore the sys and processx packages and perhaps bundle up the salient bits of this post into a script so you can occasionally check to see the 32-bit eradication progress.
