Daniele Ricci

Sorry @ameenross, but @pravi is right, although I think you made a typo: #376 refers to a different matter (maybe you meant #271?).

Recently got a more detailed stacktrace: ``` android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{bf48d4e u0 org.kontalk/.service.DownloadService} 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...

Or not: ``` android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{898d54a u0 org.kontalk/.service.msgcenter.MessageCenterService} at android.app.ActivityThread$H.handleMessage + 1872(ActivityThread.java:1872) at android.os.Handler.dispatchMessage + 106(Handler.java:106) at android.os.Looper.loop + 214(Looper.java:214) at android.app.ActivityThread.main + 7050(ActivityThread.java:7050) at...

Download and upload services were converted to JobIntentServices so this bug doesn't apply to them anymore (see 915d9e8c742ff396af4c4bb091e49866e0f046eb).

Found it! stopForeground was being called because push notifications were enabled. Related to #1278.

Still happening on beta3. Reopening.

Still happening on 4.4.0. Reopening (this is getting out of hand).

Thanks for reporting. I'm not sure this can be blamed on Kontalk since we use the tools provided by Android to do this (as a matter of fact, other apps...

(Ok so, K-9 Mail uses custom code to parse URLs because they have a custom HTML email rendering component) On that argument, [this guy has a point](https://github.com/signalapp/Signal-Android/issues/6019#issuecomment-271390509): > That means...

That's very weird, thanks for the example!