Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playback stopped when device locked or application in background #179

Open
pyby opened this issue May 10, 2021 · 2 comments
Open

Playback stopped when device locked or application in background #179

pyby opened this issue May 10, 2021 · 2 comments
Labels
bug Issue to be fix (issue and PR) - release notes section

Comments

@pyby
Copy link
Member

pyby commented May 10, 2021

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

  • Application version: 3.2.0 (dev), but probably 3.1.9 too
  • iOS / tvOS version: iOS 14.5
  • Device: iPhone Xs

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 pyby added the bug Issue to be fix (issue and PR) - release notes section label May 10, 2021
@pyby
Copy link
Member Author

pyby commented May 10, 2021

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
Copy link
Member

defagos commented Jan 7, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue to be fix (issue and PR) - release notes section
Projects
None yet
Development

No branches or pull requests

2 participants