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!!!!

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.

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.

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

I am seeing the same problem as well. I tried calling applySnapshotUsingReloadData() and apply(_,animatingDifferences: false). This causes me grief since we use the willDisplay as a trigger to fetch more data from our servers. This worked fine using traditional DataSource delegate for year.

I noticed that if I attempt to do the same in a framework created via a Cocoapod it does work, at least inside that framework. The bigger question I have is whether or not its possible to access the colors/images using the new syntax from a main project if the asset catalog exists in a framework / swift package?

I had a thought that maybe the new Settings such as ASSETCATALOG_COMPILER_GENERATE are not being inherited correctly from the project being built. So I then thought that I can add them manually to the Package.swift, but there does not appear to be "Asset Catalog Compiler" support - I do see C, CXX, Swift, and Linker support.

Update: Just grabbed Xcode 15 beta 5 and it does kind of work. I can at least get the asset symbols generated for the package, so UIColor(resource: .myblue) now works inside the package. I still cannot use UIColor.myblue from inside the package. Progress!

Can someone from Apple say whether or not SwiftData will support private, public, and shared databases when it goes live with iOS 17? Or any information regarding when it will have support in the future? I don't see the value in migrating "some" of my CoreData code to SwiftData as it just means I have two different APIs to worry about, and others on my team will have to learn both in order to support persistence. Thanks.

Sorry for the lack of additional details, but boss says I can't post any IP :( I hear what you are saying regarding what could happen in your Widgets example. We should not be in that situation, but I will triple check with our data folks to make sure the id we are using is not changing. However, if you look at the following snippet you can see that I check to make sure the itemIdentifiers array contains the item immediately before calling reconfigureItems() method. I did verify that we only operate on the items when on the main queue so there should be no threading issues. I also see the same rare crash when I was using the reloadItems() method. I will continue to scratch my head to see what is going on, but it sounds like you are saying there probably is not a problem with reconfigureItems(). Would that be accurate? var snapshot = dataSource.snapshot() if snapshot.itemIdentifiers.contains(leadModel) { snapshot.reconfigureItems([leadModel]) dataSource.apply(snapshot, animatingDifferences: true) }

Thanks. I can't remember the details but I did eventually figure it out. My original post is 3 years old and I have not figured out how to delete/close a post.

That is certainly what most people will do. So sad... Kind of defeats the purpose. Thanks for the link to your handy-dandy tool

Along the same lines, is there a correct location in a Swift Package where the PrivacyInfo.xcprivacy should go so that it can be read correctly Apple? I am seeing it in a few different locations after a Quick Look at some packages.

I heard nothing from Apple yet - luckily I was able to talk the right person to make me and admin which gets everything.

We've starting get this warning all of a sudden a couple of weeks ago as well. It says we start 13.0, but it claims it really requires 13.3 -- have not been able to determine what changed on our end to prompt such a new warning.