-
Notifications
You must be signed in to change notification settings - Fork 700
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
QuickBlox CallService Compatibility Issue on Android 14 #821
Comments
Hello @AshwiniPore
service class:
Hope it will help you. |
Hello! |
Hello @mihAdsc To solve this problem, remove the "mediaPlayback" type of the foreground service. Only types for the camera and microphone should remain android:foregroundServiceType="camera|microphone". AndroidManifest.xml
CallService.java
In addition, should obtain runtime-permissions Manifest.permission.CAMERA, Manifest.permission.RECORD_AUDIO before starting the CallService Request runtime permissions | Android Developers Let us know if the instructions provided helped you resolve your issue. |
@QB-maksym-pidhorbunskyi it worked just fine! Thank you. |
We have implemented the quickblox.service.CallService in our Android application, and it works seamlessly on versions below 14. However, upon upgrading to Android 14, we encountered functionality disruptions. To address this, we made the following changes in our code and manifest:
In the manifest file:
In the service class:
Despite these changes resolving the functionality issues, our app submission to the Google Play Store was rejected with the following reason:
Issue found: Service interruption or deferment of functionality does not have material user impact.
Details: Your app is using foreground service to Media Playback - Other when it is not required to do so.
We understand that the declared use case(s) may be interrupted or deferred by the system without creating a negative user experience. We seek guidance on how to rectify this issue while ensuring compliance with Google Play Store policies.
Your prompt assistance in resolving this matter is highly appreciated, as it is currently preventing the publication of our app on the Google Play Store.
The text was updated successfully, but these errors were encountered: