Fixed
Status Update
No update yet.
Comments
ar...@google.com
We have a fix for this and that should be released by the next Android Cast client library release.
ar...@google.com
So far we don't have a solid date when the next release will be scheduled. We will update it here or else please do check here https://developers.google.com/cast/docs/release-notes
Please Join to our group for getting a notifications on our releases :https://developers.google.com/cast/support#news_and_announcements
Please Join to our group for getting a notifications on our releases :
he...@idean.com
Ok ! Thanks for your feedback
he...@gmail.com
Did this fix ever get released? I don't see anything in the release notes about it, and it seems like others are still seeing this crash as of 2020-02-10: https://stackoverflow.com/q/60148919/9636
ar...@google.com
Yes, the fix has been released on the Android Cast SDK client library v18.0.0 (check the second item of the release notes: https://developers.google.com/cast/docs/release-notes#december-5,-2019 )
From the reported crash stack (https://stackoverflow.com/questions/60148919/large-number-of-remoteserviceexceptions-in-googles-cast-medianotificationservic ), developer still uses the Android Cast SDK client library v17.0.0. The crash should be fixed once they update to v18.0.0
From the reported crash stack (
he...@gmail.com
Thanks so much for clarifying!
mo...@gmail.com
Hi,
I am still experiencing this issue on v18.0.0. Especially on Huawei devices.
I am still experiencing this issue on v18.0.0. Especially on Huawei devices.
al...@gtempaccount.com
Hello!
We have seen a huge spike (thousands) in the number of these crashes over the past week. This has also been reported by others here:https://stackoverflow.com/questions/60148919/large-number-of-remoteserviceexceptions-in-googles-cast-medianotificationservic/60400811#60400811
Are you aware of anything that could be causing these spikes?
We have updated to 18.0.0 which seems to help, but we have found other issues with 18.0.0.
Thanks.
We have seen a huge spike (thousands) in the number of these crashes over the past week. This has also been reported by others here:
Are you aware of anything that could be causing these spikes?
We have updated to 18.0.0 which seems to help, but we have found other issues with 18.0.0.
Thanks.
he...@gmail.com
We're also still seeing the same crash on v18.0.0, but on Samsung devices running Android 8 and Android 9.
he...@gmail.com
Sorry, I should have mentioned that the crash rate is much lower now on v18.0.0.
With v17.0.0, we were seeing between 50 and 200 crashes per day on Android 8, and between 1000 and 2000 crashes per day on Android 9. Now we're seeing only around 1-5 crashes per day on both platforms.
With v17.0.0, we were seeing between 50 and 200 crashes per day on Android 8, and between 1000 and 2000 crashes per day on Android 9. Now we're seeing only around 1-5 crashes per day on both platforms.
ar...@google.com
For the issue of remoteMediaClient's mediaInfo getting nulled, I think it is not caused by the media notification change. We only passively show the media notification based on the remoteMediaClient information. But this behavior change might be caused by other changes introduced by v18.0.0. It would be very helpful if any developer could file a bug with more detailed information.
As for another report: the same crash on v18.0.0 on Samsung devices. So far we haven't received any bug reports from our internal QA or the major partners about this issue. But it is possible to cause a crash on the media notification when the receivers act abnormally. For example, the receivers keep switching between cast session on and off. In this case, the media notification will keep switching between starting notification and stopping notification. This crash happens if the notification starting/stopping too quickly. We will keep an eye on it and try to fix it as soon as possible.
As for another report: the same crash on v18.0.0 on Samsung devices. So far we haven't received any bug reports from our internal QA or the major partners about this issue. But it is possible to cause a crash on the media notification when the receivers act abnormally. For example, the receivers keep switching between cast session on and off. In this case, the media notification will keep switching between starting notification and stopping notification. This crash happens if the notification starting/stopping too quickly. We will keep an eye on it and try to fix it as soon as possible.
he...@gmail.com
Should I open a new ticket about the more rare crashes?
ar...@google.com
Please do file a new bug. Add as much information you can that can help us investigate further like crash logs and all. Once done please leave a comment here.
Description
Cast SDK version : Android Sender 16.2.0
(I checked release notes of Android Sender 17.1.0 but no bug fixes)
Here is the crash log from fabric :
Fatal Exception: android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{3ac0035 u0 com.google.android.gms.cast.framework.media.MediaNotificationService}
at android.app.ActivityThread$H.handleMessage + 2126(ActivityThread.java:2126)
at android.os.Handler.dispatchMessage + 112(Handler.java:112)
at android.os.Looper.loop + 216(Looper.java:216)
at android.app.ActivityThread.main + 7625(ActivityThread.java:7625)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run + 524(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main + 987(ZygoteInit.java:987)