Post marked as Apple Recommended
I learned that this issue also prevents independent Watch apps from accessing CMAltimeter if their parent iPhone has been updated to 17.4-17.4.1, since iPhones manage privacy settings for their companion Watches. The workaround suggested above using "CMMotionActivityManager queryActivityStartingFromDate" works for Watch apps, with the caveat that I could not find any way for my Watch app to determine the iOS version of the parent iPhone, thus it's not possible to be selective about when to invoke the workaround.
I have long thought it was somewhat disjointed the way an independent Watch app still depends on the parent iPhone to manage privacy settings -- for many reasons -- and this is one more example why it's a bad arrangement.
Post marked as Apple Recommended
I have submitted feedback FB13680923 on this issue, as I see no correct way to solve the problem from the developer side (proposed workaround is not a universal fix since not all devices support sensor recording).
Post not yet marked as solved
I filed report FB 12157657 in Feedback Assistant.
Post not yet marked as solved
Thanks for the reply -- my apps are independent Watch apps (Watch only) not related to an iPhone app, so the Automatic App Install setting doesn't have any effect on them. The one that does is in the Watch app under "App Store", but unfortunately this seems to be turned off by default and nobody thinks to look there.
I am glad to know that there is an alert directing customers to do a manual install if automatic install does not start, but it seems like customers are not paying attention to that or maybe they do not know what to do or to look on the App Store on the Watch itself. In fact, based on the contacts I get from customers, they do not understand the concept of independent Watch apps and they don't even know there is an App Store on the Watch. Three years ago I could understand this, since independent apps were new in watchOS 6, but I would have hoped customers would catch on by now.
Post not yet marked as solved
This happens with one of my watches but not the other. On my laptop I can fiddle around with some of the steps mentioned above and eventually get that Watch to make Xcode happy, but when connected to my Mac Studio it never works. Says it's waiting for the first unlock when the Watch is clearly unlocked and usable.
Post not yet marked as solved
Same issues in the Apple compass app. Those are rookie mistakes and I am surprised nobody caught this. I was also a bit mortified by the confusing UI workflow used to manage waypoints. Way too messy for a Watch app (would even be messy for an iPhone app but at least feasible).
Post not yet marked as solved
Same problem here. I finally just turned the Watch off and stopped using it, since getting work done is more important to me than wearing a Watch. I never cease to be amazed at the ways Apple can waste my time with BS like this.
Post not yet marked as solved
I don't know if this is a bug per se -- two things are happening, you are transitioning from digital zoom on one lens to optical on the next. And you are changing from a lens in one position to a lens that is slightly shifted in space (different location on the back of the phone). For a long range target, this will be almost negligible (distance between cameras << distance between lenses). When close up as you show in your video, however, it's more obvious and annoying.
Post not yet marked as solved
I don't think this will have an effect from what I am seeing, at least not as a cause -- I can see the freezes happening in an app that was never put into the background after it was launched. Launch the app, let it run and eventually the freeze will occur.
Post not yet marked as solved
I am seeing this in my apps too, and it's very sporadic. An app's AVCaptureSession can show several freezes in a 15 minute period or go hours between freezes. It's affecting my iPhone X and iPhone 11 Pro Max, both on 13.1.2. Putting the app in the background and then bringing it back to the foreground restores the AVCaptureSession every time.A couple times when this happened, I tapped the shutter button in my app and would see one of these two errors inside the "didFinishProcessingPhoto" method of my AVCapturePhotoCaptureDelegate:Error Domain=AVFoundationErrorDomain Code=-11803 "Cannot Record"Error Domain=AVFoundationErrorDomain Code=-11819 "Cannot Complete Action"That's what led me to realize that the AVCaptureSession was freezing and not simply the AVCaptureVideoPreviewLayer.
Post not yet marked as solved
I have the same question and haven't found a way to hide the logo. I will probably file a bug about this. I am also seeing some heavy-handed mapRects coming from the overlay -- when redraws are needed, they are invalidating 1536x1536 rects by default, which is extreme overkill for most purposes.
Post not yet marked as solved
Well, that was a red herring. The problem reappeared when testing the app on different iPad models in the simulator. The only one that works is the iPad Pro 9.7; on all the others, no touches are recognized. I am starting to think this is some oddness with the simulator.
Post not yet marked as solved
So the view debugger showed one view with an unexplained 2400pt height. Once I corrected that, all was well. Oddly, the other project that had the same problem also had a 2400pt high view. Projects are totally unrelated, other than both being older with XIBs. I can only assume this was some goofup in Xcode when adding the iPad target.
