I get such warnings when trying to share with ShareLink for URL item that points to a local file. I select Mail in sharing options. The last one is most interesting. LaunchServices: store (null) or url (null) was nil: Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSFunction=_LSServer_GetServerStoreForConnectionWithCompletionHandler, _LSLine=67} Attempt to map database failed: permission was denied. This attempt will not be retried. Failed to initialize client context with error Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSFunction=_LSServer_GetServerStoreForConnectionWithCompletionHandler, _LSLine=67} Could not connect to database in -[LSApplicationRestrictionsManager _LSResolveIdentifiers:]_block_invoke: Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSFunction=_LSServer_GetServerStoreForConnectionWithCompletionHandler, _LSLine=67}; resolving identifiers will only consult ManagedConfiguration Cannot attach item to mail composer without preview metadata.

I have a similar setup in which I don't understand why the conflict would take a place. I will first show the setup, and then share why I think there should not be such a conflict Linkage scheme is basic "nested dependency" case, where the dependency is static xcframework MyApp -> FirebaseAnalytics.xcframework (Static) MyApp -> MyFramework (Dynamic) -> FirebaseAnalytics.xcframework (static) I use Workspace to build MyFramework as a dependency Workspace (named HRS) * MyApp project ** MyApp target (links MyFramework.framework from Workspace -> MyFramework project) * MyFramework project ** MyFramework target When in Workspace I build MyApp, it first gives me warnings, such as duplicate output file '/Users/oleksiinezhyborets/Library/Developer/Xcode/DerivedData/HRS-etdtlgdbraymsbdmilzwmgmwkjgs/Build/Products/Debug-iphonesimulator/FirebaseAnalytics.framework' on task: ProcessXCFramework /Users/oleksiinezhyborets/Projects/tv_mobile_ios 2/MyFramework/FirebaseFrameworks/Analytics/FirebaseAnalytics.xcframework /Users/oleksiinezhyborets/Library/Developer/Xcode/DerivedData/HRS-etdtlgdbraymsbdmilzwmgmwkjgs/Build/Products/Debug-iphonesimulator/FirebaseAnalytics.framework ios simulator And then error: Multiple commands produce '/Users/oleksiinezhyborets/Library/Developer/Xcode/DerivedData/HRS-etdtlgdbraymsbdmilzwmgmwkjgs/Build/Products/Debug-iphonesimulator/FirebaseAnalytics.framework' Command: ProcessXCFramework /Users/oleksiinezhyborets/Projects/tv_mobile_ios 2/MyApp/FirebaseFrameworks/FirebaseAnalytics/FirebaseAnalytics.xcframework /Users/oleksiinezhyborets/Library/Developer/Xcode/DerivedData/HRS-etdtlgdbraymsbdmilzwmgmwkjgs/Build/Products/Debug-iphonesimulator/FirebaseAnalytics.framework ios simulator Command: ProcessXCFramework /Users/oleksiinezhyborets/Projects/tv_mobile_ios 2/MyFramework/FirebaseFrameworks/Analytics/FirebaseAnalytics.xcframework /Users/oleksiinezhyborets/Library/Developer/Xcode/DerivedData/HRS-etdtlgdbraymsbdmilzwmgmwkjgs/Build/Products/Debug-iphonesimulator/FirebaseAnalytics.framework ios simulator So, ok, I understand that Xcode and New Build System doesn't support multiple same output files. But I think it should work in such a setup because of the combination of factors: Firebase is linked statically to MyFramework, thus, at the end of MyFramework build there wouldn't be FirebaseAnalytics.xcframework in output destination. They are probably needed temporarily while build happens. Because MyApp depend on MyFramework, dependencies in the setup build serially one after another. My thought is, there is some kind of checker in Xcode that checks output files at start of a build, and if there are duplicates, it gives error right away. In this case it checks outputs of ProcessXCFramework. But in this case it's restrictive without a reason. In this case, we will have 2 steps: first MyFramework would process its Firebase xcframeworks, build the framework, and remove all the temporary xcframeworks. And then the app target would also process same xcframeworks at the same place. But as MyFramework is already build into a single binary and all temporary files are removed, there wouldn't be a conflict. Why it's a problem? It prevents from automatically rebuilding the dependent framework, and also from debugging the framework with breakpoints. Access to both these features is pretty needed for a better development. I do understand that covering different cases in build system make it even more complex, but this case seems to be pretty basic, so if I'm right that it may be fixes, it may be good if it's fixed

Hi @MobileTen. Could you please elaborate on why... Create an Xcode project for each framework. ...would work in this case?

@eskimo it would be great to have info about AMFI in docs https://developer.apple.com/documentation/driverkit/debugging_and_testing_system_extensions Endpoint Security ext wouldn't had started on my machine even with disabled SIP. Disabling AMFI helped, so it feels like kinda important instruction

Any news?

In order to fix this, we had to add second composition track and alternate between them, even tho we don't need it because we don't have transitions :(

Seems the same. Overall the implementation linked in my post is pretty simple and default, I haven't found where it could go wrong.

Sure! Here's the class that is used as ItemIdentifierType for UICollectionViewDiffableDataSource: class HashableType: Hashable {     let string: String     init(string: String) {         self.string = string     }     func hash(into hasher: inout Hasher) {         hasher.combine(string)     }     static func == (lhs: HashableType, rhs: HashableType) -> Bool {         return lhs.string == rhs.string     } }

Done! FB8381760

Does playback transition from one video to the next as expected if you just let it play (instead of seeking around)? Yes, playback is ok! Freezes only on seek. Also, it doesn't freeze if I seek quickly to middle of second video.

First of all, you have such record:"launchType == PROCESSING AND deviceActive == 1"which probably means that you shouldn't keep your device unlocked while waiting for background task.The other thing i've noticed is that chance for background launch to happen in the future is much higher if you don't kill the app from App Switcher.In our case, when app killed from switcher, ApplicationPolicy says Must not proceed for some reason:[{name: ApplicationPolicy, policyWeight: 50.000, response: {Decision: Must Not Proceed, Score: 0.00}}], FinalDecision: Must Not Proceed}