@eskimo Thanks for the prompt reply! I just tried creating a new project with the same bundle ID, even using the same team and provisioning profile, and it works fine. So it must be something specific to the app. I also tried both deleting the subsystems config file, using a default config, and then also explicitly settings specific categories for these subsystems. Still nothing. I have also tried adding a project to the same workspace, which works fine. So it must be project or target related? Additionally, I checked in the logging preferences folder and first removed the plist for the subsystem there to test. That did not affect it. I also created an explicit config for the subsystem and categories with no effects. I placed a plist with our subsystems name here: `/Library/Preferences/Logging/Subsystems/{bundleID}.plist, with this: <dict> <key>DEFAULT-OPTIONS</key> <dict> <key>Level</key> <dict> <key>Enable</key> <string>Info</string> <key>Persist</key> <string>Inherit</string> </dict> </dict> <key>analytics</key> <dict> <key>Level</key> <dict> <key>Enable</key> <string>Debug</string> <key>Persist</key> <string>Inherit</string> </dict> </dict> <key>app</key> <dict> <key>Level</key> <dict> <key>Enable</key> <string>Debug</string> <key>Persist</key> <string>Inherit</string> </dict> </dict> </dict>

Thank you for taking a look at this. I followed the suggestion about using the non-working bundle id / subsystem in the working app and visa versa, that That did not change the behavior. os_log calls also have erroneous timestamps, so it's not just a sign posts. I tried streaming the logs to the terminal, but using the subsystem predicate and process does not print anything to the terminal. Console.app does not show any results with the same filter/predicates. I'm definetly seeing other apps subsystems working as expected. log stream --signpost --process OurApp --predicate "subsystem='com.****.***.***.****'" I have also diffed the working and non-working project.pbxproj files looking for anything that stands out. I did not see anything obvious but then again, I really don't know what I would be looking for. Additionally, I removed the entire DerivedData folder, reset the package cache, and rebuilt the app. I'm not sure what else to try. I've submitted feedback with a trace of the behavior and the offending project file to https://feedbackassistant.apple.com/. Here's the Feedback id: FB11502277 Thanks!

@osxd Yes. I use the xcconfig files cocoa pods generates. I can see events emitted, but not intervals. There are two things to note in my case. Due to a legacy requiring 3rd party library, I'm forced to work with Xcode in Rosetta. The other thing which might be the cause, but I don't know the source, is that the timestamps are erroneous. They're far off in the distant future. You can see some data for the intervals in Instruments. I'd point you there, but I'm troubleshooting some weird Xcode issue, all my simulators have disappeared. I am still experiencing this issue. I gave up and intend to come back to it soon. I have a feedback thingy (ticket?) open using the Feedback Assitant app, if it's any help this is the feedback id: FB11502277 I'll be watching this thread like a hawk in the hopes that a solution is found.

I'm two years late, sorry! But for anyone else who stumbles upon this, here's a simple dynamic property. Basically just set AVPlayerController requiresLinearPlayback to true. This will prevent fast forward, rewind skip etc. It will however allow the player to pause. avPlayerViewController.requiresLinearPlayback = true