Post not yet marked as solved
I’m having the exact same issue and have been rejecter Did you manage to resolve this? It basically renders having an alarm or alert app impossible.
Post not yet marked as solved
I am having issues with the always-on screen changing the 3:44:22 to '3 hours 44 minutes' which is way too long for the widget. Has anybody managed so find a solution for this issue on the always-on screen? I notice the apple timer shows this as 3:44:-- which is a much better presentation for a widget. I understand wanting to drop the seconds update in always-on for battery life but why such a long string? Makes it unusable.
Post not yet marked as solved
Not sure if this will help some but for me I was getting this message with a WKWebView that was editable when trying to show the keyboard. It was looping endlessly. I finally managed to remove the error and use the keyboard by removing an environment variable that I had in the view that contained the WKWebView Representable. It was the following @Environment(.colorScheme) var colorScheme. Commenting this out removed the problem.
Post not yet marked as solved
The issue seems to be with projects that are in directories that syncs to your iCloud. You should create a directory in your home directory called Developer and save your projects there. Do not save projects in any directory that syncs to iCloud. that sync processor can cause issues with Xcode.
Post not yet marked as solved
Does anyone know if this issue is resolved or made better with iOS 15? I'm having the same issue. Setting the array to [] and repopulating or adding a .id(UUID()) to the list both have some tradeoffs. Notably not saving scroll position or updating the view when using NavigationLink to navigate to other views.
Post not yet marked as solved
I'm having the exact same issue. Have you found a solution to this?
Post not yet marked as solved
Salem issue when presenting form sheet over another morally presented auto or form sheet. .overContext kind of solves it but I want to know what is causing this gap and awkward sizing of navigation bar.
