We are working with Sentry crash report tool, since yesterday in an update we made with the Bitmovin android SDK version: 3.23.0 we are noticing some users getting onErrorCallback with the message: Detaching surface timed out. Here is the message on Sentry console. [Captura de Pantalla 2022-09-0…

Hi Lucky, is not a crash, we are just sending the error to our report console, but we want to know what can be the problem. Here is the stack trace. at dalvik.system.VMStack.getThreadStackTrace(VMStack.java) at java.lang.Thread.getStackTrace(Thread.java:1736) at com.riivi.riivi.crashlytics.…

thanks @gledezma . This error Detaching surface timed out can occur when detaching the rendering surface timeouts. The surface may be detached when closing playback, putting application in background and bringing it to foreground and application may also change the surface using setSurface API. To t…

Thanks for the reply @lucky.goyal Answering the questions: Several devices were triggered, here are some: [Captura de Pantalla 2022-09-20 a la(s) 15.59.30] No, our app does not use setSurface API explicitly on our code No, we weren’t able to reproduce the issue, even trying to reinit the view o…

Hi @gledezma , thanks for answers. My last question was also about the framework in which Bitmovin native Android SDK is being used in your app. Are you using any framework like React Native or Flutter, I guess the answer is no, can you please confirm? This issue is also reported in general for Exo…

Hi, @lucky.goyal Oh sorry, my bad, but the answer is no, no frameworks, only kotlin and native android. We tested with the newest version, we did an update and the issue seems to be reduced or maybe gone. We will be monitoring, but for now, all is ok. Thank you very much. Edit: impact data Fro…

We don’t know what fixed this issue, but is not appearing anymore. Close this thread if you want.

Hi @gledezma , thanks for the update. Glad that the issue seems to be resolved. I believe the main change was to upgrade to latest player version. Thanks again for reporting this. This is helpful information for other community members.

Update: A fix is added since Bitmovin Android player SDK 3.30.0 to address Detaching Surface timed out error.

Some users are getting onError event with "Detaching surface timed out."

Support

lucky.goyal (Lucky Goyal) September 11, 2022, 12:09pm 2

Hi @gledezma ,

Thanks for asking your query here. In general OnErrorCallback is fired by Bitmovin player SDK when a playback error occurs. This should not result in an application crash or crash report.

Can you please share the full Stack Trace(there is option to view stack trace in the screenshot you shared) to help us understand the issue further?

Topic		Replies	Views
[AndroidTV] Getting Video codec error from MediaCodecRenderer Support bitmovin-player , android , bitmovin	2	3193	May 14, 2023
Caused by: java.lang.IllegalArgumentException: The surface has been released by MediaCodecVideoRenderer Support bitmovin-player , bitmovin-encoding , android , bitmovin	4	1270	May 11, 2023
Offline playback failed in Android 12 and 13 using Android SDK Support bitmovin-player , android , bitmovin	6	777	December 8, 2022
Facing inconsistent errors in the player, same video when played again does play Support android	1	721	October 30, 2023
Facing DRM error on older Android devices like Pixel C, what's the issue and how to solve it? Discussion drm , android , widevine	4	2809	November 16, 2022

Some users are getting onError event with "Detaching surface timed out."

Related topics