Post

Replies

Boosts

Views

Activity

Reply to iOS 16.0 beta 7 broke Text(Date(), style: .timer) in SwiftUI widgets
I just commented above things seem to be working... but I remembered the always on display and decided to try it out. (On the simulator only). When I have my Lock Screen timer widget running and lock the simulator (from the menu), the display changes from a timer to something like "<1 minute" and just stays there without changing. When I unlock the device (but not return to the home screen) the widget shows the time again (like, "0.45", but it does not change after that (it no longer counts on the Lock Screen). Beyond the frozen counter issue, is the always-on Lock Screen not going to allow counting in real time and instead just show an approximate time (with units)? I really did not leave enough room for units in my widget.
Sep ’22
Reply to iOS 16.0 beta 7 broke Text(Date(), style: .timer) in SwiftUI widgets
It isn't working correctly for me in iOS 16.1 beta 1 (on a physical device). Initially both the Home Screen and Lock Screen widget timer fields do work. However, once I have shown the Lock Screen and go back to the Home Screen widget, the timer has frozen. If I completely lock the phone, then unlock it, the Lock Screen timer changes to the elapsed time, but is no longer actively counting. Returning to the app seems to get the timers going again... until the Lock Screen is shown, then the timers freezes again.
Sep ’22
Reply to iOS 16.0 beta 7 broke Text(Date(), style: .timer) in SwiftUI widgets
I had submitted feedback to Apple regarding this issue. The feedback has been marked "Investigation complete - Unable to diagnose with current information". This was my first feedback submission to Apple... and to be honest, it wasn't the best feedback -- I could see this resolution being just a way to close my feedback. I did not include any logs files (or any files). I described as best I could the situation with the ".timer" style Text field no longer automatically counting (in Home and Lock Screen widgets). I wasn't sure how to provide steps to reproduce this... as the API component configuration just doesn't function (as it was). Anyway, I'm just adding my experiences to this thread. I'm curious if any of you have had better luck with your feedback. (And if you have any pointers on better feedback, I'll take 'em)
Sep ’22