add me to the list

Same problem on Safari. On Chome, it works OK.

Thank you. Here is my feedback number FB11364016 as well. Strangely, the problem does not appear on iPad (with iPadOS 16.1 beta 1 (20B5027f), released the same day). So perhaps the implementations are different according tot he device, or the bug is already fixed.

This is bad news... :( I can confirm this too. I wish Apple developers would read their forum / submitted feedbacks (which we spend time and energy on), and just say if the bug is under their radar. OS regressions are the worst, and put us in a very awkward position with our app users.

Feedback assistant says that there are more than 10 recent similar reports, so at least they are aware about the problem (since someone merged them). I'm also worried about the bug not being fixed before the non beta release, but this is a good sign.

From another related post: @ricob : "Hi, we are aware of the issue. Please follow the iOS 16 beta release notes for updates on when this will be fixed."

This is so bad. I'm preparing a new (degraded) version of my apps in case they don't fix it.

OK ... so ... it seems that the public version of iOS16, being the same as RC1, still contains the bug. Let's get ready for support emails from unhappy customers, and bad reviews from the App Store 😞. (I read that iOS 16.1 is scheduled for November...)

Indeed, the problem is not fully solved on iOS 16.1 beta 1.

16.1 Beta 2, same problem.

While it is much better, I still have the stop of the timer with iOS 16.1 Beta 3 from times to times (but it is hard to reproduce as it is quite random) Playing with the phone by going to the some pages after, some pages before, locking the screen, can make the issue appear. But changing the page again will make the timer continue at next display.

4 years later, yes it helped ! Thank you :)

I had the same problem with Version 14.2 (14C18). As suggested, in a previous post, "git status" (in terminal) revealed that one file was still marked as modified, although it had been comitted by Xcode. This was the problem causing Xcode crash.

I also have the same problem. PHImageManager requestImageForAsset does not return an HDR image from an HDR video in the library. Note : Similarly, AVAssetImageGenerator does not return an HDR image from an HDR AVAsset.

I have the same problem with quick clicks in my widget: sometimes the app opens when the button is pressed. Strangely, I can't reproduce it with the Emoji Rangers sample code from Apple (you should try if it's the same for you). I don't understand why, as I have tried to display the same content in my app as the Emoji Rangers one, but I still have the problem. I'm speculating here, but maybe the button click is ignored when the timeline provider loads the updated data, but the widget still responds to the clicks to open the app.