Posts

Post not yet marked as solved
4 Replies
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.
Post not yet marked as solved
4 Replies
That is certainly what most people will do. So sad... Kind of defeats the purpose. Thanks for the link to your handy-dandy tool
Post not yet marked as solved
2 Replies
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.
Post not yet marked as solved
2 Replies
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) }
Post marked as solved
5 Replies
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.
Post not yet marked as solved
1 Replies
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!
Post not yet marked as solved
5 Replies
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.
Post marked as solved
6 Replies
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.
Post marked as solved
3 Replies
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.
Post marked as solved
6 Replies
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!!!!
Post not yet marked as solved
1 Replies
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.
Post marked as solved
4 Replies
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.
Post marked as solved
6 Replies
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).
Post marked as solved
4 Replies
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!