Search results for

“SwiftData inheritance relationship”

4,980 results found

Post

Replies

Boosts

Views

Activity

Reply to DriverKit. Data Integrity issue.
There are no DispatchSync calls in our code. Here is the SCMD_DONE: Actually, there is, it's just implicit. Correlating your code with the crash log: Thread 8: ... 2 SCSIControllerDriverKit 0x195e8b364 IOUserSCSIParallelInterfaceController::ParallelTaskCompletion(OSAction*, SCSIUserParallelResponse, int (*)(OSMetaClassBase*, IORPC)) + 156 3 com.mycompany.driverkit.MyDevice 0x1042a6a20 invocation function for block in OsBridge::SCMD_DONE(void*, megasas_cmd_fusion*, SCSIUserParallelResponse*, megasas_cmd_fusion*) You're here: ghc->ivars->sentQueue->DispatchAsync(^{ -> ghc->ParallelTaskCompletion(act, lResp); I don't know enough about the exact details of how you've configured your queues to be certain about what's going on, but I suspect what's going on is that ParallelTaskCompletion is implicitly targeting the crashing thread: Thread 5 Crashed:: : 0 libdispatch.dylib 0x19671aa8c __DISPATCH_WAIT_FOR_QUEUE__ + 484 1 libdispatch.dylib 0x19671a5d0 _dispatch_sync_f_slow + 152 2 DriverKit 0x195d3fc1c
Oct ’25
Flutter 3.35 iOS build fails on Apple Silicon (M3/M4): 'Flutter/Flutter.h' file not found
I'm on a MacBook Air 2025 M4 (Apple Silicon) using Flutter 3.35.5 on channel stable, Xcode 26.0.1, and CocoaPods 1.16.2. Actual Setup: Component Version macOS 15.0 Sequoia CPU Apple M4 (ARM64) Flutter 3.35.5 on channel stable Dart 3.9.2 DevTools 2.48.0 CocoaPods 1.16.2 Xcode 26.0.1 Build 17A400 Since updating Flutter from 3.24 → 3.35, iOS builds consistently fail with the following errors (not matter if simulation or real device, also ios version no matter): fatal error: 'Flutter/Flutter.h' file not found Error logs: /Users/myuser/.pub-cache/hosted/pub.dev/app_links-6.4.1/ios/app_links/Sources/app_links/AppLinksIosPlugin.swift /Users/myuser/.pub-cache/hosted/pub.dev/app_links-6.4.1/ios/app_links/Sources/app_links/AppLinksIosPlugin.swift:1:8 Unable to find module dependency: 'Flutter' import Flutter ^ flutter_native_splash /Users/myuser/.pub-cache/hosted/pub.dev/flutter_native_splash-2.4.6/ios/flutter_native_splash/Sources/flutter_native_splash/include/flutter_native_splash/FlutterNativeSplashPlugin.h /Users/m
1
0
177
Oct ’25
Unable to enable Apple Pay for App Clip – “relationship 'undefined'” error when adding capability
Hey everyone, hoping someone here has run into this before. I have a fully functional App Clip (com.didyoucatchit.app.Clip) linked to my main app (com.didyoucatchit.app). The Clip builds and runs perfectly, but I’m seeing issues trying to enable Apple Pay for it. When I try to link my Merchant ID under the “On Demand Install Capable” capability in the Apple Developer portal, I get this error: A relationship in the provided entity is not allowed for this request. The relationship 'undefined' can not be included in a 'bundleIdCapabilities' request. Here’s what I have already configured and confirmed: App Clip capabilities in Xcode include: Apple Pay Payment Processing Associated Domains (appclips:app.didyoucatchit.com) Provisioning profile includes: Apple Pay Payment Processing Associated Domains In-App Purchase On-Demand Install Capable Entitlements file for the Clip: com.apple.developer.associated-domains appclips:app.didyoucatchit.com com.apple.developer.in-app-payments merchant.com.didy
0
0
166
Oct ’25
Reply to Creating Swift Package with binaryTarget that has dependencies
Let's examine this log: objc[39953]: Class _TtC10KingfisherP33_6AA794C9C370CDB07604B4D8B99AEAA312BundleFinder is implemented in both /Users/Name/Library/Developer/Xcode/DerivedData/TestApp-capvhjiqxrdgdnbevpkajicnjpcs/Build/Products/Debug-iphonesimulator/WallpaperKit.framework/WallpaperKit (0x100e8bbf8) and /Users/Name/Library/Developer/CoreSimulator/Devices/E0AF13C2-874C-47B9-B864-72AF3E4D5D4B/data/Containers/Bundle/Application/AF32011A-92E7-4E26-9A97-9F0C25C07863/TestApp.app/TestApp.debug.dylib (0x101a543b0). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. You have mangled Swift class names there, and they exist in two places, so the system doesn't know which implementation to use. While the crux of your question is Why are these symbols still given an _implementationOnly import, there's something subtle here — this log is being generated by the Objective-C runtime, for a Swift class — notice the system logging this is named objc at the fron
Oct ’25
Reply to Share Extension Lifetime and SwiftData
If you are using SwiftData + CloudKit in both your main app and extension, which uses NSPersistentCloudKitContainer under the hood, I'd start with pointing you the following technote: Avoid synchronizing a store with multiple persistent containers Please feel free to follow up with further questions, if any. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Oct ’25
Share Extension Lifetime and SwiftData
I have an app that uses a Share Extension that allows the user to share videos, from Files and Photos etc., the video URL and some related data is then persisted with SwiftData and synchronized with CloudKit. This code has worked consistently for a long time although recently, with iOS 26 and recent builds of iOS 18, I have observed that the video is either not saved to SwiftData (iOS 26.0), or available locally when the app is opened on the same device where the share occurred, but not synchronized to other devices (iOS 18.7 and iOS 26.1 beta). Assuming the video is opened locally after being shared into the app, it is typically synchronized with CloudKit to other devices although it's not as reliable as it should be. Is there a reliable approach in the Share Extension to ensure that the data is saved to the local SwiftData database and then synchronized with CloudKit. I suspect it could be that the lifetime of the Share Extension has become even more constrained in recent OS updat
1
0
193
Oct ’25
Reply to Using SwiftData with a local and CloudKit backed configuration at the same time
Thanks for providing the project. The issue happens because you don't specify a name for your model configurations. When using multiple configurations, give each configuration a unique name so SwiftData knows how to separate the data and schema. The following code fixes the issue: let fullSchema = Schema([ LocalModel.self, RemoteModel.self, ]) let localSchema = Schema([LocalModel.self]) let localConfig = ModelConfiguration(Local, schema: localSchema, cloudKitDatabase: .none) let remoteSchema = Schema([RemoteModel.self]) let remoteConfig = ModelConfiguration(Remote, schema: remoteSchema, cloudKitDatabase: .automatic) container = try ModelContainer(for: fullSchema, configurations: localConfig, remoteConfig) Best, —— Ziqiao Chen  Worldwide Developer Relations.
Oct ’25
Best Practices for Using CKAssets in Public CloudKit Database for Social Features
Hello Apple Team, We are looking at developing an iOS feature on our current development that stores user-generated images as CKAssets in the public CloudKit database, with access control enforced by our app’s own logic (not CloudKit Sharing as that has a limit of 100 shares per device). Each story or post is a public record, and users only see content based on buddy relationships handled within the app. We’d like to confirm that this pattern is consistent with Apple’s best practices for social features. Specifically: Is it acceptable to store user-uploaded CKAssets in the public CloudKit database, as long as access visibility is enforced by the app? Are there any performance or quota limitations (e.g., storage, bandwidth, or user sync limits) that apply to CKAssets in the public database when used at scale? Would CloudKit Sharing be recommended instead, even if we don’t require user-to-user sharing invitations? For App Review, is this model (public CKAssets + app-enforced access control) compliant w
2
0
215
Oct ’25
Reply to How can I give my documents access to Model Foundation
Hi @Julien458, The Foundation Models Framework itself does not provide a direct way to search your documents. There are two ways your app might go about achieving this functionality: Your app could first identify pertinent documents/information by, for example, querying a database or using an API. Then, your app would include this information as part of the prompt to Foundation Models. Alternatively, your app could provide Foundation Models with a Tool that does this same sort of query action, and Foundation Models could then call on this Tool whenever it is relevant to do so based on the prompt. How you go about searching for the most relevant information is up to you and depends on how your app's data is structured, and there's no one right answer here. You might first take a look at SwiftData. Or if you want to take it a step further and perform on-device semantic searches, look into vector embeddings with CoreML or the Natural Language Framework. Best, -J
Oct ’25
Reply to Shared modelContainer between DocumentGroup and WindowGroup
I'm also looking for a way to do this. I assume that it's not possible with the currently released version of SwiftData/SwiftUI, and that you'd need to drop back to manually sharing a model container somehow, or present the content that should have been in a separate window in a sheet, meaning you can't present more than one at a time. It's quite limiting.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Oct ’25
Reply to Using SwiftData with a local and CloudKit backed configuration at the same time
Hi, Thank you very much, I've pushed a minimal project which fails to GitHub: https://github.com/thomasleese/swiftdata-local-and-remote-sample If you run it, you should find the following error: SwiftData/ModelContext.swift:3699: Fatal error: Failed to identify a store that can hold instances of SwiftData._KKMDBackingData from [8B7D97A6-4C92-49AD-9C78-17D04917B135: SwiftData.DefaultStore] I haven't tried yet with two separate model containers, although I think this will be tricky because a lot of the views requires a combination of models from both stores.
Oct ’25
Reply to SwiftData ModelActor causes 5-10 second UI freeze when opening sheet
I experimented with this more, by removing increasingly larger portions of the interaction with SwifData, and finally realized: the freezes are caused by the Xcode debugger session, and have nothing to do with SwiftData or ModelActor. I saw the not reporting this hang messages in the logs, but didn't realize what Xcode was trying to tell me. If it instead said something like hang likely caused by the debugger session it would have been much easier to understand than not reporting.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Oct ’25
Reply to Error accessing backing data on deleted item in detached task
Yeah, this is an interesting topic. Consider the following flow: In a background task that runs for long time, you fetch a SwiftData model object and hold it for later use. In the main queue, the object is deleted via user interaction. In a background task, you access the object. Based on the current implementation of SwiftData, step 3 will trigger an error because the object was deleted. In the Core Data world, you can use query generations to guarantee the object being valid in step 3, as discussed in Accessing data when the store changes. In the case where, from a managed object context pinned to a generation, you change a piece of data that has been changed, saving the context triggers a conflict, which you can handle via NSMergePolicy. SwiftData doesn't have query generations, and so I don't see an ideal pattern to handle the kind of issue. I may consider the following: a. Avoid accessing a same piece of data simultaneously by shorten the time window. Concretely: In the backgro
Oct ’25
Reply to How to handle required @relationship optionals in SwiftData CloudKit?
Sorry for not being clear. As an example, assuming you have some SwiftUI views that render the relationship, and the views accept only an non-optional array, it will make sense that your SwiftData model creates a computed property to wrap relationship. Here, the Swift views are the other part of your app that prefers to consume a non-optional array. I hope this makes the point clear. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Oct ’25
Reply to How to handle required @relationship optionals in SwiftData CloudKit?
SwiftData + CloudKit uses NSPersistentCloudKitContainer under the hood, which requires all relationships must be optional. For more information, see Creating a Core Data Model for CloudKit. The requirement exists because of the latency of the synchronization: When you create an object graph in device A, which is being synchronized to device B, the system doesn't guarantee to synchronize the whole graph all at once. As a result, it's possible that an object is synchronized but its relationship is not. This situation is expressed as the relationship being nil. By checking if the relationship is nil, the app instance running on device B can consume the object appropriately. In your case, wrapping a relationship with a computed property to return an empty array if nil makes sense to me, if the other part of your app prefers to consume an empty array. It doesn't matter if the data is big or small. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Oct ’25
Reply to DriverKit. Data Integrity issue.
There are no DispatchSync calls in our code. Here is the SCMD_DONE: Actually, there is, it's just implicit. Correlating your code with the crash log: Thread 8: ... 2 SCSIControllerDriverKit 0x195e8b364 IOUserSCSIParallelInterfaceController::ParallelTaskCompletion(OSAction*, SCSIUserParallelResponse, int (*)(OSMetaClassBase*, IORPC)) + 156 3 com.mycompany.driverkit.MyDevice 0x1042a6a20 invocation function for block in OsBridge::SCMD_DONE(void*, megasas_cmd_fusion*, SCSIUserParallelResponse*, megasas_cmd_fusion*) You're here: ghc->ivars->sentQueue->DispatchAsync(^{ -> ghc->ParallelTaskCompletion(act, lResp); I don't know enough about the exact details of how you've configured your queues to be certain about what's going on, but I suspect what's going on is that ParallelTaskCompletion is implicitly targeting the crashing thread: Thread 5 Crashed:: : 0 libdispatch.dylib 0x19671aa8c __DISPATCH_WAIT_FOR_QUEUE__ + 484 1 libdispatch.dylib 0x19671a5d0 _dispatch_sync_f_slow + 152 2 DriverKit 0x195d3fc1c
Replies
Boosts
Views
Activity
Oct ’25
Flutter 3.35 iOS build fails on Apple Silicon (M3/M4): 'Flutter/Flutter.h' file not found
I'm on a MacBook Air 2025 M4 (Apple Silicon) using Flutter 3.35.5 on channel stable, Xcode 26.0.1, and CocoaPods 1.16.2. Actual Setup: Component Version macOS 15.0 Sequoia CPU Apple M4 (ARM64) Flutter 3.35.5 on channel stable Dart 3.9.2 DevTools 2.48.0 CocoaPods 1.16.2 Xcode 26.0.1 Build 17A400 Since updating Flutter from 3.24 → 3.35, iOS builds consistently fail with the following errors (not matter if simulation or real device, also ios version no matter): fatal error: 'Flutter/Flutter.h' file not found Error logs: /Users/myuser/.pub-cache/hosted/pub.dev/app_links-6.4.1/ios/app_links/Sources/app_links/AppLinksIosPlugin.swift /Users/myuser/.pub-cache/hosted/pub.dev/app_links-6.4.1/ios/app_links/Sources/app_links/AppLinksIosPlugin.swift:1:8 Unable to find module dependency: 'Flutter' import Flutter ^ flutter_native_splash /Users/myuser/.pub-cache/hosted/pub.dev/flutter_native_splash-2.4.6/ios/flutter_native_splash/Sources/flutter_native_splash/include/flutter_native_splash/FlutterNativeSplashPlugin.h /Users/m
Replies
1
Boosts
0
Views
177
Activity
Oct ’25
Unable to enable Apple Pay for App Clip – “relationship 'undefined'” error when adding capability
Hey everyone, hoping someone here has run into this before. I have a fully functional App Clip (com.didyoucatchit.app.Clip) linked to my main app (com.didyoucatchit.app). The Clip builds and runs perfectly, but I’m seeing issues trying to enable Apple Pay for it. When I try to link my Merchant ID under the “On Demand Install Capable” capability in the Apple Developer portal, I get this error: A relationship in the provided entity is not allowed for this request. The relationship 'undefined' can not be included in a 'bundleIdCapabilities' request. Here’s what I have already configured and confirmed: App Clip capabilities in Xcode include: Apple Pay Payment Processing Associated Domains (appclips:app.didyoucatchit.com) Provisioning profile includes: Apple Pay Payment Processing Associated Domains In-App Purchase On-Demand Install Capable Entitlements file for the Clip: com.apple.developer.associated-domains appclips:app.didyoucatchit.com com.apple.developer.in-app-payments merchant.com.didy
Replies
0
Boosts
0
Views
166
Activity
Oct ’25
Reply to Creating Swift Package with binaryTarget that has dependencies
Let's examine this log: objc[39953]: Class _TtC10KingfisherP33_6AA794C9C370CDB07604B4D8B99AEAA312BundleFinder is implemented in both /Users/Name/Library/Developer/Xcode/DerivedData/TestApp-capvhjiqxrdgdnbevpkajicnjpcs/Build/Products/Debug-iphonesimulator/WallpaperKit.framework/WallpaperKit (0x100e8bbf8) and /Users/Name/Library/Developer/CoreSimulator/Devices/E0AF13C2-874C-47B9-B864-72AF3E4D5D4B/data/Containers/Bundle/Application/AF32011A-92E7-4E26-9A97-9F0C25C07863/TestApp.app/TestApp.debug.dylib (0x101a543b0). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. You have mangled Swift class names there, and they exist in two places, so the system doesn't know which implementation to use. While the crux of your question is Why are these symbols still given an _implementationOnly import, there's something subtle here — this log is being generated by the Objective-C runtime, for a Swift class — notice the system logging this is named objc at the fron
Replies
Boosts
Views
Activity
Oct ’25
Reply to Share Extension Lifetime and SwiftData
If you are using SwiftData + CloudKit in both your main app and extension, which uses NSPersistentCloudKitContainer under the hood, I'd start with pointing you the following technote: Avoid synchronizing a store with multiple persistent containers Please feel free to follow up with further questions, if any. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Oct ’25
Share Extension Lifetime and SwiftData
I have an app that uses a Share Extension that allows the user to share videos, from Files and Photos etc., the video URL and some related data is then persisted with SwiftData and synchronized with CloudKit. This code has worked consistently for a long time although recently, with iOS 26 and recent builds of iOS 18, I have observed that the video is either not saved to SwiftData (iOS 26.0), or available locally when the app is opened on the same device where the share occurred, but not synchronized to other devices (iOS 18.7 and iOS 26.1 beta). Assuming the video is opened locally after being shared into the app, it is typically synchronized with CloudKit to other devices although it's not as reliable as it should be. Is there a reliable approach in the Share Extension to ensure that the data is saved to the local SwiftData database and then synchronized with CloudKit. I suspect it could be that the lifetime of the Share Extension has become even more constrained in recent OS updat
Replies
1
Boosts
0
Views
193
Activity
Oct ’25
Reply to Using SwiftData with a local and CloudKit backed configuration at the same time
Thanks for providing the project. The issue happens because you don't specify a name for your model configurations. When using multiple configurations, give each configuration a unique name so SwiftData knows how to separate the data and schema. The following code fixes the issue: let fullSchema = Schema([ LocalModel.self, RemoteModel.self, ]) let localSchema = Schema([LocalModel.self]) let localConfig = ModelConfiguration(Local, schema: localSchema, cloudKitDatabase: .none) let remoteSchema = Schema([RemoteModel.self]) let remoteConfig = ModelConfiguration(Remote, schema: remoteSchema, cloudKitDatabase: .automatic) container = try ModelContainer(for: fullSchema, configurations: localConfig, remoteConfig) Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Oct ’25
Best Practices for Using CKAssets in Public CloudKit Database for Social Features
Hello Apple Team, We are looking at developing an iOS feature on our current development that stores user-generated images as CKAssets in the public CloudKit database, with access control enforced by our app’s own logic (not CloudKit Sharing as that has a limit of 100 shares per device). Each story or post is a public record, and users only see content based on buddy relationships handled within the app. We’d like to confirm that this pattern is consistent with Apple’s best practices for social features. Specifically: Is it acceptable to store user-uploaded CKAssets in the public CloudKit database, as long as access visibility is enforced by the app? Are there any performance or quota limitations (e.g., storage, bandwidth, or user sync limits) that apply to CKAssets in the public database when used at scale? Would CloudKit Sharing be recommended instead, even if we don’t require user-to-user sharing invitations? For App Review, is this model (public CKAssets + app-enforced access control) compliant w
Replies
2
Boosts
0
Views
215
Activity
Oct ’25
Reply to How can I give my documents access to Model Foundation
Hi @Julien458, The Foundation Models Framework itself does not provide a direct way to search your documents. There are two ways your app might go about achieving this functionality: Your app could first identify pertinent documents/information by, for example, querying a database or using an API. Then, your app would include this information as part of the prompt to Foundation Models. Alternatively, your app could provide Foundation Models with a Tool that does this same sort of query action, and Foundation Models could then call on this Tool whenever it is relevant to do so based on the prompt. How you go about searching for the most relevant information is up to you and depends on how your app's data is structured, and there's no one right answer here. You might first take a look at SwiftData. Or if you want to take it a step further and perform on-device semantic searches, look into vector embeddings with CoreML or the Natural Language Framework. Best, -J
Replies
Boosts
Views
Activity
Oct ’25
Reply to Shared modelContainer between DocumentGroup and WindowGroup
I'm also looking for a way to do this. I assume that it's not possible with the currently released version of SwiftData/SwiftUI, and that you'd need to drop back to manually sharing a model container somehow, or present the content that should have been in a separate window in a sheet, meaning you can't present more than one at a time. It's quite limiting.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to Using SwiftData with a local and CloudKit backed configuration at the same time
Hi, Thank you very much, I've pushed a minimal project which fails to GitHub: https://github.com/thomasleese/swiftdata-local-and-remote-sample If you run it, you should find the following error: SwiftData/ModelContext.swift:3699: Fatal error: Failed to identify a store that can hold instances of SwiftData._KKMDBackingData from [8B7D97A6-4C92-49AD-9C78-17D04917B135: SwiftData.DefaultStore] I haven't tried yet with two separate model containers, although I think this will be tricky because a lot of the views requires a combination of models from both stores.
Replies
Boosts
Views
Activity
Oct ’25
Reply to SwiftData ModelActor causes 5-10 second UI freeze when opening sheet
I experimented with this more, by removing increasingly larger portions of the interaction with SwifData, and finally realized: the freezes are caused by the Xcode debugger session, and have nothing to do with SwiftData or ModelActor. I saw the not reporting this hang messages in the logs, but didn't realize what Xcode was trying to tell me. If it instead said something like hang likely caused by the debugger session it would have been much easier to understand than not reporting.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to Error accessing backing data on deleted item in detached task
Yeah, this is an interesting topic. Consider the following flow: In a background task that runs for long time, you fetch a SwiftData model object and hold it for later use. In the main queue, the object is deleted via user interaction. In a background task, you access the object. Based on the current implementation of SwiftData, step 3 will trigger an error because the object was deleted. In the Core Data world, you can use query generations to guarantee the object being valid in step 3, as discussed in Accessing data when the store changes. In the case where, from a managed object context pinned to a generation, you change a piece of data that has been changed, saving the context triggers a conflict, which you can handle via NSMergePolicy. SwiftData doesn't have query generations, and so I don't see an ideal pattern to handle the kind of issue. I may consider the following: a. Avoid accessing a same piece of data simultaneously by shorten the time window. Concretely: In the backgro
Replies
Boosts
Views
Activity
Oct ’25
Reply to How to handle required @relationship optionals in SwiftData CloudKit?
Sorry for not being clear. As an example, assuming you have some SwiftUI views that render the relationship, and the views accept only an non-optional array, it will make sense that your SwiftData model creates a computed property to wrap relationship. Here, the Swift views are the other part of your app that prefers to consume a non-optional array. I hope this makes the point clear. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Oct ’25
Reply to How to handle required @relationship optionals in SwiftData CloudKit?
SwiftData + CloudKit uses NSPersistentCloudKitContainer under the hood, which requires all relationships must be optional. For more information, see Creating a Core Data Model for CloudKit. The requirement exists because of the latency of the synchronization: When you create an object graph in device A, which is being synchronized to device B, the system doesn't guarantee to synchronize the whole graph all at once. As a result, it's possible that an object is synchronized but its relationship is not. This situation is expressed as the relationship being nil. By checking if the relationship is nil, the app instance running on device B can consume the object appropriately. In your case, wrapping a relationship with a computed property to return an empty array if nil makes sense to me, if the other part of your app prefers to consume an empty array. It doesn't matter if the data is big or small. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
Oct ’25