Fixed
Status Update
Comments
sy...@google.com <sy...@google.com> #2
Thanks for reporting the issue. This failure could happen if you are not using the notification provided by Cast SDK and using your own custom notification. Usually, the app would be considered as a foreground app if you are not using the notification provided by Cast SDK and it is free to start any service.
To mitigate the issue, you can disable the auto reconnect service:https://developers.google.com/android/reference/com/google/android/gms/cast/framework/CastOptions.Builder.html#setEnableReconnectionService(boolean)
You can also refer to bug 73718071 if it helps.
Please share the below details if you are unable to figure out the root cause or unable to fix the issue.
1. Do you use the Notification provided by Cast SDK?
2. How does the app provides playback control when the app goes to background?
3. Did you receive this report from all Android devices?
4. Is it a Android version specific or Device specific from your reports?
5. Any other details
To mitigate the issue, you can disable the auto reconnect service:
You can also refer to
Please share the below details if you are unable to figure out the root cause or unable to fix the issue.
1. Do you use the Notification provided by Cast SDK?
2. How does the app provides playback control when the app goes to background?
3. Did you receive this report from all Android devices?
4. Is it a Android version specific or Device specific from your reports?
5. Any other details
b....@gmail.com <b....@gmail.com> #3
Thank you for the update. We don't use the notification provided by the Cast SDK. If we turn off the ReconnectionService will that impact us greatly, is there any way we can keep the benefits of the reconnection service while using our own notification?
sy...@google.com <sy...@google.com> #4
Generally, Cast SDK starts re-connection service when the media starts (https://developers.google.com/android/reference/com/google/android/gms/cast/framework/media/RemoteMediaClient.Callback.html#onStatusUpdated() ).
The workaround, for the apps that are using their own notification service is to post the notification before the cast media starts. If you can't do that then you can disable the re-connection service for now. We are working on this issue and will address it in the future releases.
The workaround, for the apps that are using their own notification service is to post the notification before the cast media starts. If you can't do that then you can disable the re-connection service for now. We are working on this issue and will address it in the future releases.
b....@gmail.com <b....@gmail.com> #5
Thats great to know, thanks for the help.
sa...@gmail.com <sa...@gmail.com> #6
How ReconnectionService can impact us here if we disable it. I'm getting the same issue with my application.
@OP: What's the best workaround have you applied?
@OP: What's the best workaround have you applied?
sy...@google.com <sy...@google.com> #7
This issue is fixed and available to public in v16.0.2. Please refer to below release notes for more details.
Release notes:https://developers.google.com/android/guides/releases#septemper_5_2018
Release notes:
ty...@gmail.com <ty...@gmail.com> #8
VBucks fortnite
Description
Please answer all relevant questions below so that we have enough information to investigate your issue. Providing incomplete information will delay investigation of your issue.
Bug Report Template
Describe the issue: expected vs. observed behavior and/or appearance.
ReconnectionService is trying to start a service in the background. This is causing an IllegalStateException on Android 8+.
com.google.android.gms.cast.framework.ReconnectionService }: app is in background uid UidRecord{c51b1af u0a131 TPSL bg:+2m55s135ms idle change:cached procs:1 seq(0,0,0)}
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1577)
at android.app.ContextImpl.startService(ContextImpl.java:1532)
at android.content.ContextWrapper.startService(ContextWrapper.java:664)
at com.google.android.gms.internal.cast.zzai.zzg$1385ff(Unknown Source:19000)
at com.google.android.gms.internal.cast.zzai.onStatusUpdated(Unknown Source)
at com.google.android.gms.cast.framework.media.zzr.onStatusUpdated(Unknown Source:30)
at com.google.android.gms.internal.cast.zzdh.onStatusUpdated(Unknown Source:6)
at com.google.android.gms.internal.cast.zzdh.zza(Unknown Source:14000)
at com.google.android.gms.cast.framework.media.RemoteMediaClient.zzb(Unknown Source:2)
at com.google.android.gms.internal.cast.zzct.run(Unknown Source:31)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6669)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
List steps to reproduce the issue, if known.
We have been unable to reproduce locally but it is our largest crash.
Which version of the Cast SDK are you using?
15.0.1
On which version(s) of the OS (iOS, Android) do you observe the problem?
Android
On which device type(s) such as phones, tablets or laptops (iPad, iPhone, etc.) do you observe the problem?
Android devices
Do you observe the problem when running on a physical device, or the simulator, or both?
We haven't reproduced, but it happens on user devices.
If this is a device discovery or device connectivity issue: Do you observe the problem over Cellular (using Guest Mode), WiFi (using either Guest Mode or local connection), or both?
If this is strictly a UI appearance/styling issue, please take screenshot(s) (for iOS, and Android) illustrating the problem and attach them to the bug report. Also mention whether the problem occurs in portrait orientation, landscape orientation, or both.
If this is not a UI appearance/styling issue, please capture logs from the SDK for a time interval leading up to and including the occurrence of the problem, and attach them to the bug report. For issues relating to device discovery, the log should cover at least 20 seconds. For issues relating to device connectivity, the log should cover the entire time during which you attempted to start a Casting session.
Obtaining iOS Cast SDK Logs:
Obtaining Android Cast SDK Logs: