Any update on this? A technical reply would be appreciated.

I'm asking about the role (Developer, App Manager, etc), not how to provide credentials. Passwords and API Keys are mutually exclusive.

There isn't any official word that things are different with other devices, but the truth is they don't need to be because the underlying partition scheme (like GPT) has taken a back seat to APFS containers and volumes. All disk/volume advances in recent years (10.13+) have been for APFS itself, like the readonly system volume (Volume Groups, firmlinks), etc.

How are you checking the postinstall script is failing? Are you examining /var/log/install.log (also in Console.app) to see if there are any messages? In general, the environments for package scripts are restricted, I would be surprised if "/usr/bin/env bash" is runnable there.

You might want to post some notes from the crash report if you want a workaround

I wasn't able to do it in System Preferences, and did sudo softwareupdate -ia in Terminal. It will automatically restart once it's ready though, so be aware.

Not entirely sure what you're asking, but if you want to trace filesystem events on macOS, try fs_usage(1) - x-man-page://fs_usage

It would be best to post the error messages from the log here (they will likely describe the exact issue), but you might just try changing the interpreter to "/bin/bash". Normally macOS installers don't open installed targets on the user's behalf (installers just install), and the only other case would be to load and start a service, which usually involves launchctl(1).

If you mention something specific you can't figure out, it might help point you in the right direction. Having said that, the tide has really gone out on documentation for some parts of macOS, so checking the Archive - https://developer.apple.com/library/archive/navigation/ for examples might help.

Could you talk a little bit about why you want to open files in ~/Documents without the user having given prior permission? You wouldn't be able to enumerate the directory without access anyway?

Depending on the situation, it might be that the text is accidentally the same color as its background, hasn't been rendered in the right place (clipping), or is suffering from some kind of compositing problem. Is the text selectable?

The phrase "system software" usually means kernel extensions (drivers, in Windows-speak), so the place to look would be System Information > Software > Extensions. Having seen this before, it's likely you're using policy-restricted extensions which would have (or did) present warnings in Catalina. These are now deprecated, and while a boot argument can be used to reenable them in the beta, they will likely be permanently disabled in the release. The list of extensions will indicate which aren't loadable (look for Unsupported, and not from Apple), and you'll find that the list to be enabled in System Preferences excludes these. The way it currently works is all third party extensions get rebuilt in a collection (documented in kmutil(8) - x-man-page://kmutil), so everything gets retriggered.

Are you sure you set execute permissions on what you're trying to execute? chmod(1) - x-man-page://chmod is important

Depending which Fortran compiler you're using, it may put leading and trailing underscores in the symbol names. If everything compiled correctly, there may be a mismatch in the names

Someone will provide a more knowledgeable answer, but it looks like only text comes across right now. GeometryReader/ResolvedShapeView/etc don't emit anything, maybe because they're implemented GPU-side when possible (like a fill with masking, CoreAnimation-style). If you want to always be able to access accurate PDF representations, try CoreGraphics.