I have a simple tvOS app that has a single audio track, a storyboard with single scene that contains a button for play/pause toggling.I am trying to add Siri Remote handling so that user can play/pause the track with remote's "toggle play/pause" button.The problem, though, is that when the application starts it doesn't respond to remote control events if the AVPlayer is paused. When user starts playback using the touch-button on Siri Remote I can pause the playback using "toggle play/pause" button. I CAN'T start playback again after the track has been paused.I tried two approaches:application.beginReceivingRemoteControlEvents()MPRemoteCommandCenter.shared().pauseCommand.addTarget(...)Using the remoteControlReceived(with event: UIEvent?) I receive the event only when the AVPlayer is playing and the event's subtype is pause command.Using the remote command center I registered for pauseCommand, playCommand and togglePlayPauseCommandcommands but only pauseCommand is being triggered when the playback is active.Am I missing something?

I'm getting crashes when I'm using `EmptyView` as a root of `NavigationView`. Here's the minimum code I managed to get to reproduce the crash:struct ContentView: View { var body: some View { NavigationView { EmptyView() } } }

I have a very weird bug where very often Xcode can't find products in local packages and my build fails. Is there a way to at least somehow stabilize the search? I have a very long list (>50) of remote packages added to the workspace and reset a cache takes a very long time and doesn't always help.

I suddenly started to receive the following email with the error in it stating that my uploaded app is not available to be used in TestFlight: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at “MyApp.app/Contents/PlugIns/MyAppWidgetExtension.appex” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' It was all working fine and now I am not sure even where to start looking. Signing, provisioning and everything else is managed automatically.