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

Stop using foreground service for Read Aloud feature. #4041

Closed
MohitMaliFtechiz opened this issue Oct 18, 2024 · 0 comments · Fixed by #4027
Closed

Stop using foreground service for Read Aloud feature. #4041

MohitMaliFtechiz opened this issue Oct 18, 2024 · 0 comments · Fixed by #4027
Assignees
Milestone

Comments

@MohitMaliFtechiz
Copy link
Collaborator

Describe the bug
We do not need to use the foreground service for the RealAloud feature, since the readAloud feature only runs when the reader screen is active if we move to another screen, or close the application then readAloud stops so we do not need to use the foreground service for this.

We have a ticket #4026 where uploading the application on playStore failed and we have to explain to playStore why and where we are using foreground service in our application and what the impact is on the user. By removing the readAloud service from our code we do not need to give an explanation to playStore about this service, and we directly upload the application on the Play Store (At least all the custom apps). Also, using the foreground service for readAloud is not ideal since we do not need to use this.

Expected behavior
We should use normal service instead of foreground service.

Environment

  • Version of Kiwix Android: 3.11.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment