Your ImageJ installation cannot be updated because it is read-only

[JoblessLoser]

Hi,

Many thanks for making this available.
We have been making use of this to feed fiji into munki for some time.

The code adds Fiji to munki as expected and new installations work without issue however they fail (or appear to fail) to update.

The update runs once when a new version is available (rather than running and the failing and remaining as an outstanding update in munki).
When the update runs the next time you open Fiji in gives the message.

"Your ImageJ installation cannot be updated because it is read-only"

The "about" ImageJ continues to show the older version.

Googling the issue suggest that running....

sudo chflags -R nouchg /Applications/Fiji.app
sudo xattr -rd com.apple.quarantine /Applications/Fiji.app

...would fix the problem, however it does not and the application files do not appear to have chflags or com.apple.quarantine extension attributes set.
(I have been running these commands as a pre and post install script all the same)

uninstalling and reinstalling Fiji works without bring up the "Your ImageJ installation cannot be updated because it is read-only" error although "about" ImageJ continues to show the older version number.

I partly suspect that Fiji has been updated but "about" ImageJ continues to show the first version of fiji installed on the computer.

Unfortunately being IT support I don't actually use fiji so I don't know enough to check if the reported version number in "about" fiji is accurate.

Any help would be greatly appreciated, I have tried to resolve the issue in the past by asking in imagej forums.

[vmiller]

Interesting. Like you I know nothing about Fiji other than how to deploy it. I've not had any reports from my user base, but it wouldn't be the first time problems went unreported...

[vmiller]

I'm not sure there is anything here to be fixed in the autopkg recipe. I really don't want random users on a lab system to be able to update Fiji/ImageJ - that's munki's job. The thing to do would be to set ImageJ to not check for updates. I'm not sure that is possible to do at this present time...

See this ImageJ issue : imagej/imagej-updater#7