Update: I noticed that if touch the screen the animation completes and the entire current cell is displayed as expected.

In an eventually consistent distributed system you can never "know" that you have existing data or devices in the cloud. Your application will simply "find out at some point" that this data exists and needs to be designed to handle that. You statement is from the perspective of a computer scientist, not from that of a user. And its all about the user, all the time in the real world. I've had many complaints from users that my app seems to have lost data - yes the user is being impatient and not waiting an infinite amount of time for the initial sync. But it should would be nice if we could trigger an initial sync or at least know that its happening so we can inform the user that "be patient, data is on its way to your device".

Thanks for the reminder, had meant to file the request but zoned out. Yes, I can create my own UI for editing, but that does not excuse the missing feature when Apple is trying to get us to replace one component with another. If there is a good reason for the missing feature then it would be nice to know what the reason is.

Done (a while ago, but I forgot to reply earlier)

Done. (a while ago, but I forgot to reply here) thanks.

Actually the hack that uses KVO does not work with iOS 14. The fonts just get changed to something weird, definitely not what you were trying to set.

I watched the SwiftUI Accessibility: Beyond the Basics session and like what I saw, but it did not address my question regarding support for LargeContentViewer on custom views. I have a scenario in one of the apps I am working on - actually trying to decide to do the whole thing in SwiftUI or stick with UIKit for now - that requires some views that cannot change size. Am going through a checklist of components and accessibility features that I feel are must have to aid in my SwiftUI vs UIKit decision.

I have the same question/comment.

My bad, after submitting the question I realized I had set the boundarySupplementaryItems property on the entire layout instead of on the sections...

I am also seeing the same issue whereas tapping "Keep" does not ask the user if they want them delivered prominently or quietly. It does have a button asking for showing them in a summary - but I as a user do not have summaries turned on. Tapping the summary button does not enable summaries either. I am trying to convince people we should switch over of using "provisional" notifications to be better iOS clients, but this issue will never get past the product department's scrutiny.

Beta 2 of Xcode and iOS.

Update: I just tried with Xcode and iOS beta 3 and got the same crash.

I don't know if its the solution, but when I changed my apple-app-site-association file to a different structure (both seem to work fine for regular universal links. Did not work for ShareWithYou { "applinks": { "details": [ { "appIDs": ["ABCDEFGHIJK.com.hotngui.ItsAlmostTime"], "components": [ { "/": "/mobile/*", "comment": "Universal links" } ] } ] } } This structure does work: { "applinks": { "apps": [], "details": [ { "appID": "ABCDEFGHIJK.com.hotngui.ItsAlmostTime", "paths": [ "/mobile/*" ] } ] } }

I just tried again with Xcode 14 beta 4 / iOS 16 beta 4 - same crash. I do now get the following in the debugger console. I do not use continuations in this particular app and it shows up when I tap the ShareLink. _Concurrency/CheckedContinuation.swift:184: Fatal error: SWIFT TASK CONTINUATION MISUSE: data(contentType:) tried to resume its continuation more than once, throwing exportFailed! 2022-07-27 11:19:58.818137-0700 ItsAlmostTime[575:16531] _Concurrency/CheckedContinuation.swift:184: Fatal error: SWIFT TASK CONTINUATION MISUSE: data(contentType:) tried to resume its continuation more than once, throwing exportFailed!

I checked that and it's not the issue. There is a issue where I have different "App ID Prefix" values between my main app and extensions caused by the age of my developer account. Apparently in the olden days the App ID Prefix was not the Team ID. I have contacted Apple and they are looking into fixing the issues (as per an old Tech Note).