Is the Legacy App reporting under Systems Report Always Accurate?

[jaybar]

I am beginning to question the 32 bit warning system in Mojave. I installed a 32 bit app from Cisco (AnyConnect) and upgraded to their 64 bit version and I still get warnings.

More alarming was the i then uninstalled the app and it still appears in the legacy part of my systems report.

Both are concerning.

Thanks

 

[chabig]

The entry in Legacy Software shows the path to the app. Go see if it exists.

 

[KALLT]

The “legacy software” section in System Information is neither up-to-date nor comprehensive. It seems to list just those programs that you have used recently and it takes some time to clear the list.

However, if you are still getting a warning when opening a program then this might indicate that there is still a component that is not 64-bit. At least I have not encountered this.

 

[martyjmclean]

A "64-bit app" may still have 32-bit dependencies or helper apps. I work in Avid Media Composer, which is like that.

Try running

system_profiler SPApplicationsDataType | grep -B 6 -A 2 "(Intel): No" > ~/Desktop/non64bit.txt

in Terminal instead?

 

[jaybar]

A "64-bit app" may still have 32-bit dependencies or helper apps. I work in Avid Media Composer, which is like that.

Try running

system_profiler SPApplicationsDataType | grep -B 6 -A 2 "(Intel): No" > ~/Desktop/non64bit.txt

in Terminal instead?

There is something very strange and I hope someone can comment. I upgraded the app (Cisco AnyConnect) to the latest version, which is supposedly 64 bit and fully compatible with Mojave. It still appears in the system report under “legacy”.

However, when I install the same version on my High Sierra partition, which shipped with my iMac, the same app is listed as 64 bit. Moreover, all the component (helper) apps are also listed as 64 bit.

How can it be 32 bit it one OS and 64 bit in the other. Identical versions of the app in both instances.

 

[NoBoMac]

How can it be 32 bit it one OS and 64 bit in the other. Identical versions of the app in both instances.

How it seems to behave, if you invoke something that is 32-bit, it's basically logging this and staying in the log.

Case in point, I tried to invoke Office 2011 on my new Mac (TimeMachine restored), could not due to activation server issues. Deleted Office as really don't need, yet, still shows up in the list of Legacy software (been off the machine for over a month now).

 

[jaybar]

How it seems to behave, if you invoke something that is 32-bit, it's basically logging this and staying in the log.

Case in point, I tried to invoke Office 2011 on my new Mac (TimeMachine restored), could not due to activation server issues. Deleted Office as really don't need, yet, still shows up in the list of Legacy software (been off the machine for over a month now).

It’s more complex. If I run it today in the Mojave volume, it appears under legacy, with today’s date. It I run it today in the High Sierra volume, it lists it as a 64 bit app. Both run today.