Animate the swift ui view, not the hosting controller.

Not sure what will possess you to do this but the language is not meant to be used like this.

Time to switch to SwiftUI. Just make sure it is part of the copy bundle resources located under build phases. If it is not then re-add it to the project.

Do it all over again as a non-admin user of the Mac.

You're not going find much of anything on Carbon due to deprecation since os X 10.8 https://developer.apple.com/documentation/coreservices/carbon_core and Xcode 5 https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemFrameworks/SystemFrameworks.html#//apple_ref/doc/uid/TP40001067-CH210-BBCFGHBB

It seems like you can only deploy standalone watch apps (FB13480884).

Resubmit it again

Just wait for iOS 17.3. In the future all non-developer related content -> https://discussions.apple.com/welcome

It's not about being rounded. It's about suppressing everything after the 2nd decimal place using the format specifier %.2f if you wanted to show the nth position after the decimal place then %.3f will show 1.255, %.5f will show 1.25500 etc etc. 1.255 will not round because there is nothing carry over. 1.256 will round because there is a 1 to carry over.

Beta software. Anything is possible until the formal Release Candidate has been published unless you're testing or evaluating your apps against pre-release software, which this question doesn't sound like. You should never install beta releases on your everyday devices.

Any crashes outside the doings of the SDK are of your making and responsibility due to the misuse of data types and memory access or incorrect memory management. Your question sounds a bit vague and assumptuous. Please provide a use case in the form of a coded example with which you might be having an issue.

Cubase is a non-apple product and should be reported to the developers of Cubase via their support channels.

There is only one way to find out - let us know how it goes.

Does it make a difference if you open the file in binary mode vs ascii? FILE *fp = fopen(filename, "ab+");

Instead of writing byte by byte to the file you already have the buffer in mAudioData. Why not just write the entire data buffer to the file stream when the callback events are raised?