The ActivityKit API requires developers to parameterize calls to pushToStartTokenUpdates by the live activity's attributes, e.g.
for await data in
Activity<AdventureAttributes>.pushToStartTokenUpdates {
// Send token to server.
}
for await data in
Activity<BoringAttributes>.pushToStartTokenUpdates {
// Send token to server.
}
At runtime, I have noticed that the token is the same for the different live activity attribute types we support in our app.
Can someone confirm if this behavior is consistent? If the pushToStartToken is the same across different live activity types, it can simplify our database design 🙏🏼.
ctibbs
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Hey all,
I'm following the instructions in https://developer.apple.com/documentation/xcode/setting-up-storekit-testing-in-xcode to set up mock in-app purchases in my project.
In the section Prepare to Validate Receipts in the Test Environment it says to create a StoreKit certificate and mentions using conditional compilation to use that certificate:
#if DEBUG
let certificate = "StoreKitTestCertificate"
#else
let certificate = "AppleIncRootCertificate"
#endif
Where would I indicate to use that certificate? I don't think it's picking it up, since
my calls to Bundle.main.appStoreReceiptURL are returning nil when I'm debugging.