SRGSSR / playsrg-apple

The Play SRG applications for iOS and tvOS
https://srgssr.github.io/playsrg-apple/
MIT License
44 stars 3 forks source link

Playback stopped when device locked or application in background #179

Open pyby opened 3 years ago

pyby commented 3 years ago

Issue type

Incorrect behavior

Description of the problem

Some SRF and RTS users reported in AppStore reviews that the audio is not planing in background. I experimented for the first time the same issue.

Audio is expected to continue. I don't know why, it stopped.

Same issue with audio and video (If video in background enabled) The PiP button in the Letterbox player is not displayed. In other applications on the same device, the PiP button is displayed.

Killing the application and relaunched it fixed the issue.

Environment information

Reproducibility

Difficult to reproduce

Steps to reproduce

  1. Play an audio (AoD or livestreams)
  2. Lock the device or put the application in background.

Audio is expected to continue. Bu it stopped.

But it's not enough to reproduce the issue.

pyby commented 3 years ago

As discussed with @defagos , it could be an issue in SRGMediaPlayer.

I tried to connect the debugger. But as we deployed nighty version in a release mode, I'm not sure that we can attach a debugger.

Could not attach to pid : “38180”
Domain: IDEDebugSessionErrorDomain
Code: 3
Failure Reason: attach failed (Not allowed to attach to process.  Look in the console messages (Console.app), near the debugserver entries when the attached failed.  The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.)
User Info: {
    DVTRadarComponentKey = 855031;
    RawUnderlyingErrorMessage = "attach failed (Not allowed to attach to process.  Look in the console messages (Console.app), near the debugserver entries when the attached failed.  The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.)";
}
defagos commented 2 years ago

We recently have several complaints about this issue in App Store reviews, but this is likely a device issue which can be fixed with a restart.