Yes it’s codesigned all properly, or I imagine Apple would not accept it for the AppStore. It’s iOS only, so the Mac stuff shouldn’t be a problem.
Sits very strange. It’s a problem only with this one user so far. On Thu, Dec 30, 2021 at 11:02 PM Bernie Maier via Coreaudio-api < [email protected]> wrote: > On Fri, 31 Dec 2021, at 11:29 AM, J Navarro via Coreaudio-api wrote: > > I have had issues in the past with users not being able to see my AUv3 > plugin when first installed. Usually a reboot fixes the problem. > > I currently have a user who has installed my app, restarted, and even > reset his device, and cannot see my app. I can see it just fine on my > devices, so I can’t really reproduce the issue. Does anyone know what could > be happening? Am i labeling something wrong in the app bundle maybe? Thanks. > > > Asking the probably obvious here, but your plugin is all correctly > code-signed, right? The reason I ask is that one of the things I do is help > another developer port plugins to macOS. We haven't taken the AUv3 leap > yet, but we've had reports (and I've reproduced) that some of our older > plugins aren't visible on M1 Macs running Monterey (whereas they did appear > correctly in other setups). These old plugins were built before > code-signing for plugins became absolutely mandatory, and signing them > fixed the issue. > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Coreaudio-api mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > > https://lists.apple.com/mailman/options/coreaudio-api/oblitteraa%40gmail.com > > This email sent to [email protected] > -- -- Sonic Kat
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
