Hi, We are currently using xcframework dependencies in our large project and we've got a compile time of ~15min on CircleCI. We are trying to move a few dependencies from xcframework to Swift Package Manager but I'm seeing that there is a lot of time being added to our compile time as xcodebuild will always compile spm also. I've tried caching SourcePackage to limit the download steps but I wasn't able to find a way to cache the spm dependency builds also. Is this possible ? What is the strategy of compiling large projects with multiple SPM dependencies on a CI system.

Hi, We are currently looking to implement some basic reporting on the server for our apps in app purchases but we are struggling to find the necessary information in the App Store Server API [1] Currently our flow works like this: on the app we are successfully buying a subscription our server is configured to receive App Store Server Notifications for StoreKit 2 server receives callbacks correctly for the transactions we are performing on the app side What we would like to achieve is to be able to know on the server how much money we would earn from the subscription bought by the user. Can you please help us out with the following? Is there an api that can tell us that a given in app purchase product is linked to a certain price tier ? If a user payed for a subscription, how can we tell on the server if the 1.99$ price tier will have a 30% or 15% fee from AppStore depending on the subscription duration ? Is there a way to tell if that subscription is in the second year or not ? [1] https://developer.apple.com/documentation/appstoreserverapi

My current iOS 13+ (xcode 12.5) simplified project setup has some nested dependencies as follows: Alamofire.xcframework -- is linked into - Internal-Framework-A Alamofire.xcframework -- is linked into - Internal-Framework-B Internal-Framework-A -- is linked into - AppTarget (actual application target) Internal-Framework-B -- is linked into - AppTarget Because Alamofire.xcframework is being linked into multiple internal frameworks, it will be linked without actual embedding. This means that AppTarget will need to link and embed Alamofire.xcframework so that the internal frameworks can dynamically link it at runtime. Internal frameworks compile correctly with this setup but AppTarget doesn't compile and it's trowing the follow error:  Multiple commands produce ... Command: ProcessXCFramework and the reason for that being: on compile time AppTarget compiles Internal-Framework-A that triggers the ProcessXCFramework for Alamofire.xcframework but because AppTarget also has Alamofire.xcframework as dependency it will also run the ProcessXCFramework command, so we will have 2 commands for the same file. I'm curious to know if there is something that I'm missing. It would look like there should be a flag for xcode to process the same framework once.

Hi, I have a working SCNSceneView on my screen and what I'm trying to do is to dynamically load on screen a .scn file. I'm currently performing the following: language if let node = SCNReferenceNode(url: url) { node.load() self.sceneView?.prepare([node], completionHandler: {  _ in    self?.sceneView?.scene.rootNode.addChildNode(node) print("added child node") }) } I've tried a lot of other iterations where I'm calling load or prepare on a background DispatchQueue but my conclusion is that no matter what I try addChildNode(node) will freeze the screen until it finishes it's operation. Did you find a solution for this issue ?