Ok, I looked at the WebRTC source code from the GitHub project, and there is no AppKit support, just UIKit. If you target a macOS app with macCatalyst, then any derived or subclassed UIView or UIKit-based view or controller subclassed view like RTCEAGLVideoView and RTCMTLVideoView will use the correct symbols. For macOS support using the swift package is going to call for a separate Xcode project targeting macCatalyst. For example: UIView class type is UIKit only. To get this on macOS you will have to use a macCatalyst target. open class RTCEAGLVideoView : UIView, RTCVideoRenderer { weak open var delegate: RTCVideoViewDelegate? public init(frame: CGRect, shader: RTCVideoViewShading) public init(coder aDecoder: NSCoder, shader: RTCVideoViewShading) /** @abstract Wrapped RTCVideoRotation, or nil. */ open var rotationOverride: NSValue? }

Have you tried enabling Rosetta support in Xcode if using an Apple Silicon device?

Just make isShowing private if it has no external purpose.

As per the feedback directive on the GitHub repo: All feedback should be directed via the feedback assistant -> https://feedbackassistant.apple.com/

You might have better luck using the AVFoundation API for reading and writing audio to the file system. https://developer.apple.com/documentation/avfaudio/audio_engine/performing_offline_audio_processing

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?

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

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

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

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.

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.

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.

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

Resubmit it again

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