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

ForegroundServiceStartNotAllowedException #88

Closed
4 tasks done
XilinJia opened this issue Sep 10, 2024 · 3 comments
Closed
4 tasks done

ForegroundServiceStartNotAllowedException #88

XilinJia opened this issue Sep 10, 2024 · 3 comments

Comments

@XilinJia
Copy link
Owner

XilinJia commented Sep 10, 2024

Checklist

  • I have used the search function for OPEN issues to see if someone else has already submitted the same bug report.
  • I have also used the search function for CLOSED issues to see if the problem is already solved and just waiting to be released.
  • I will describe the problem with as much detail as possible.
  • If the bug only to occurs with a certain podcast, I will include the URL of that podcast.

App version

6.5.9

Where did you get the app from

Other

Android version

14

Device model

Samsung

First occurred

recently

Steps to reproduce

Play an episode in queue,
put Podcini in background or turn off screen,
when the next episode in queue starts, notification panel likely not show up,
this is when ForegroundServiceStartNotAllowedException shows in Logcat,
Podcini may keep playing, or may get stopped by the system sometime later.

This is noticed on Samsung Android 14 devices.

This relates to long-standing issues reported to media3: androidx/media#111
and to Android: https://issuetracker.google.com/issues/307329994

Expected behaviour

No response

Current behaviour

No response

Logs

No response

@XilinJia
Copy link
Owner Author

XilinJia commented Oct 2, 2024

Since Google can't resolve this issue for over 2 years, I don't expect that they be able to do it soon. So from now on the workaround is to build apk's with target SDK set to 30 (Android 11), though build and tests will be with the most recent SDK's and Android versions (for now SDK 35 and Android 14).

Please report any irregularities.

@XilinJia
Copy link
Owner Author

Looks like the best approach is to have an apk targeted to Android 15 and request unrestricted permission from the user.

@XilinJia
Copy link
Owner Author

with unrestricted activity permission, this is worked around. close for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant