I uninstalled XCode and updated to the latest version (13.4) and it seems to have resolved.
jarradcutting777
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Yeah I need to prevent screen rotation while the user is recording video, but with deprecation of shouldAutorotate I don't know how to do this. setNeedsUpdateOfSupportedInterfaceOrientations doesn't seem to be found when trying to compile and supportedInterfaceOrientations is read only. Currently, I've got a bunch of iOS16 users complaining.
Seeing this in iOS 15, too.
If anyone is still confused with this, make sure you check the ORDER of your subscriptions within your subscription group in AppStoreConnect. You are specifically asked to order them in descending order, the first being the subscription with the most benefits, down to the subscription with the least benefits. They are easy enough to adjust if you need.
By doing this, you can be guarenteed that if a user upgrades from subscriptionA to subscriptionB, then subscriptionB will be listed in the latest receipt information when receiving a server notification or validating a receipt. If you get the order incorrect, you will have users trying to upgrade, but being stuck on the subscription with less benefits because your server will not see any higher subscription.
For me, I've found this happens on projects that share a module and it helps to only be working with one at a time.
In saying that though, when this message was displaying it looked like it the build had hung, but in fact, the build had failed with error messages ages before - it's just I didn't realise because it also had the "preparind editor" message so I thought the build was still running. Check your build process is actually still running, fix any errors if any, and hit build again (even if this message is still displayed).
I achieved this the same way you would record a video from a camera really - AVAssetWriter. The only difference being your captured frame CVPixelBuffers don't come from an AVCaptureSession, they come from your ARFrames which are provided to you in the session(_:,didUpdate:) callback.
Same here. jtw.io can interpret the signature but it has the invalid error.