This is a legacy code and I don't think there is any specific reason for using /Resources/Components/We tried placing the legacy extension in Content/PlugIns, but the warning is still not resolved. (***.safariextz is not a valid product / component package.)Any other inputs that we could try.

I am also seeing the similar behaviour that sudo commands are failing from post or pre install scripts.

Install version N then update to N+1 (C) is failing, Yes our tests are on a VM, each time reverting to a snapshot where product is never tested.

Our version N is not code signed (code object is not signed at all) and to meet the notarisation requirements, N+1 is code signed and meets the DR, we see the following messages when codesign -v -v -R run on N+1 valid on disk satisfies its Designated Requirement explicit requirement satisfiedThe issue here is System Prefernces showing as checked but API(AXIsProcessTrustedWithOptions) returning not trusted, after the update if app is not trusted for any reason(code signture compatibility etc), System Prefereces is expected to show it as unchecked so that user can check it .Right now what is happening, when we guide the users to check the box next to our app, they see it as already checked and not doing anything resulting in app not trusted.

Anyone got any clue or a work around for this problem, to get the installer plugins working on Mac OS Big Sur

Looks like installer plugins are working as expected on beta 4 of macOS Big Sur

Starting beta3 of Mac OS Big Sur, the version is getting reported as 11

kmutil load is also not returning any error to indicate that it needs user approval.

We try to get other hardware information as well, not just the CPU info. This information is used to know the hardware info of the system where our app is run.(tried with sysctl -n machdep.cpu.brand_string, even this is not returning any value)

>> For reporting purposes? Or because you runtime decisions based on that info? For reporting purposes

>>Re-reading your initial email, I think I might’ve got the wrong end of the stick here. Are you trying to get the native (Arm) CPU information? Or the emulated (Intel) CPU info? We are trying to get native (Arm) CPU information, but from an emulated app. Is this not possible? Basically we want to report it as Apple processor if the hardware is Apple processor, (About Mac .. it shows as Apple A12Z ), but how can the same be read/found from an emulated app.

Thank you for the pointers, but looks like posixspawnattrsetarchpref_np is available with Xcode 12, our code is not yet compatible with Xcode 12. and the documentation says that it sets the preferred architecture. we don't want to set it but just report the hardware info.

it's the same on beta9 too

logged a bug https://feedbackassistant.apple.com/feedback/8892034

We have resolved this issue by creating assets with 1x and 2x