android.app.RemoteServiceException: while trying to manage foreground service

[vkryl]

Well-established and the most reported crash. It happens frequently in calls and while playing music, most likely usually without user even noticing.

It seems that is either something is improperly managed by Telegram X, or this crash is coming from some bugged Android versions.

As of 27th March 2020 there were 50,047 reports, 19,633 impacted users.

Saving this issue here in 2021 in case somebody would like to investigate this issue and build a solid conclusion on why this happens.

android.app.RemoteServiceException: 
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881)
  at android.os.Handler.dispatchMessage (Handler.java:105)
  at android.os.Looper.loop (Looper.java:164)
  at android.app.ActivityThread.main (ActivityThread.java:6942)
  at java.lang.reflect.Method.invoke (Method.java)
  at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)

[vkryl]

Occasionally reproduces on high-end Samsung Galaxy S22 Ultra. Noticeable only on debug builds on app launch, as background crashes are invisible to user on Samsung devices by default.

Stack trace for commit 758bb7a:

=== Stack Trace Dump ===
Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{8fbffcc u0 org.thunderdog.challegram/.service.ForegroundService}
android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{8fbffcc u0 org.thunderdog.challegram/.service.ForegroundService}
	at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2245)
	at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2216)
	at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2508)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8762)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

[vkryl]

Current guesses:

1. Foreground notification hides too fast after being shown, so system doesn't track that the notification was actually shown and there's no reason to force crash from the system side
2. Foreground service is being started while main thread is frozen for some reason, so foreground notification isn't shown
3. (Unlikely) Bug in foreground notification detection in the system

It's possible that none of them are correct, just leaving for whatever found solution in future.

[Saminkamoje2810]

android.app.RemoteServiceException:
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881)
at android.os.Handler.dispatchMessage (Handler.java:105)
at android.os.Looper.loop (Looper.java:164)
at android.app.ActivityThread.main (ActivityThread.java:6942)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)

[Saminkamoje2810]

Well-established and the most reported crash. It happens frequently in calls and while playing music, most likely usually without user even noticing.

It seems that is either something is improperly managed by Telegram X, or this crash is coming from some bugged Android versions.

As of 27th March 2020 there were 50,047 reports, 19,633 impacted users.

Saving this issue here in 2021 in case somebody would like to investigate this issue and build a solid conclusion on why this happens.

android.app.RemoteServiceException: 
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881)
  at android.os.Handler.dispatchMessage (Handler.java:105)
  at android.os.Looper.loop (Looper.java:164)
  at android.app.ActivityThread.main (ActivityThread.java:6942)
  at java.lang.reflect.Method.invoke (Method.java)
  at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)

#58 (comment)

[Ami22r]

e41c48d

[Dmabhisir]

WhatsApp bot

[Dmabhisir]

• @Dmabhisir @vkryl @Saminkamoje2810

~~```

---

[mohammadjnb136-ux]

Well-established and the most reported crash. It happens frequently in calls and while playing music, most likely usually without user even noticing.

It seems that is either something is improperly managed by Telegram X, or this crash is coming from some bugged Android versions.

As of 27th March 2020 there were 50,047 reports, 19,633 impacted users.

Saving this issue here in 2021 in case somebody would like to investigate this issue and build a solid conclusion on why this happens.

android.app.RemoteServiceException: 
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881)
  at android.os.Handler.dispatchMessage (Handler.java:105)
  at android.os.Looper.loop (Looper.java:164)
  at android.app.ActivityThread.main (ActivityThread.java:6942)
  at java.lang.reflect.Method.invoke (Method.java)
  at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)