it becomes unresponsive if the resources need to sync between apple iCloud and the temporary folder compounded by internet speed and size of each object.

Align your perspective with reality and the privacy alignment of APIs Apple is trying to move towards.

CTCarrier is deprecated since iOS 16.0 and will be returning stubbed data.

In North America medical advice is regulated hence you're either a medical institution or a licensed doctor providing such information or proof that the work was done on behalf of such. Hence the rejection. Each case is a special case meaning you don't know what the other developers provided to Apple prior to Approval.

Not allowed due to privacy considerations.

Rosetta support was removed if building on Apple Silicon. So your C++ library might need to be rebuilt for arm64 or Apple Silicon. In my opinion Xcode 14.3 RC is not ready for prime time as it has trouble launching on Intel as well.

Are you building a product for a financial institution that does this? Or just raising this as a general concern? The product has been built and in use for many years now.

What I also noticed with Xcode 14.3 on intel vs Apple Silicon is for example in the follow sample code deprecated messages aren't being surfaced under Apple Silicon . /// Access the bytes in the data. /// /// - warning: The byte pointer argument should not be stored and used outside of the lifetime of the call to the closure. @available(swift, deprecated: 5, message: "use `withUnsafeBytes<R>(_: (UnsafeRawBufferPointer) throws -> R) rethrows -> R` instead") public func withUnsafeBytes<ResultType, ContentType>(_ body: (UnsafePointer<ContentType>) throws -> ResultType) rethrows -> ResultType /// Calls the given closure with the contents of underlying storage. /// /// - note: Calling `withUnsafeBytes` multiple times does not guarantee that /// the same buffer pointer will be passed in every time. /// - warning: The buffer argument to the body should not be stored or used /// outside of the lifetime of the call to the closure. @inlinable public func withUnsafeBytes<ResultType>(_ body: (UnsafeRawBufferPointer) throws -> ResultType) rethrows -> ResultType

Did you set up any Microphone permission entries in the info plist?

Sometimes it will load other times just won't

Financial institutions also use this API as a means to combat fraud. The alternative to deprecation could have been an entitlement request based on a genuine use case just certain Wifi APIs.

It’s pretty much an AP from my ISP that is fairly new. Will file the bug report. Thanks.

Probably try injecting JS as well to reload the page.

Read the API documentation, read the human interface guide ...

Sorry, please report your WhatsApp issue to META. These are the risk encountered when using Beta software for everyday uses before an officially supported release.