We need those dSYM files back as well... Please make them available again.

I do not deal with SWCollaborationMetadata at all in my code. I will say that there did to be some times during debugging where I was not getting my delegate called, or it took a lot of time before it got called. I don't think I am seeing issues now that its in production, but will continue to monitor.

I just tried Xcode Beta 6 and iOS beta 7 -- no change. Will this be fixed before production? If I do not have a chance to verify that it works before I submit to the App Store I will have to remove the functionality from my app. It turns out that it is working now, but just not the way I expected. It looks like the query only uses the "date" and returns 24 hourly forecasts when I specify a start/end date that is the same. Hmmm.

Ok, multiple problems: AppID issues, resolved by Apple Needed to update add WeatherKit to Capability and App Services in Identifiers up on App Store website Needed to install updated provisioning profiles (debug and release) Now I am able to get responses from the API!!!!

Am having the same complaint regarding your #1 and #2 points. I've filed an enhancement request for #2 along with the fact that its forced to full screen after talking to Apple engineers in a WWDC Lab Session.

Using Xcode 14 beta 5 I no longer get the crash. However, now when I include the SharePreview the list of apps for sharing contains nothing except an action to create a quick note.

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).

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 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/*" ] } ] } }

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

Beta 2 of Xcode and iOS.

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.

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

I have the same question/comment.

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.