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 🙏🏼.