Closed cee-dee closed 3 weeks ago
@cee-dee Maybe you can add a breakpoint on the constructor of the class kotlin.coroutines.jvm.internal.BaseContinuationImpl
to try to figure out when this class loads initially.
Thank's for the awesome speed of your support! I've already tried to set breakpoints, but either no breakpoint actually breaks, or it never reaches the init block of my App.
This setup with emulated breakpoints (basically) never reaches the init block:
Do you have a concrete suggestion of where I should set breakpoints?
Is there anything else I can try to find the cause?
@cee-dee Just released SD version 2.4.1 with a big rework for Android. From now on SD for Android requires only the Gradle plugin and no other dependencies or method calls are required.
I've got this
IllegalStateException
although I'm usingDecoroutinatorRuntime.load()
in theinit { }
block of myApplication
class. In order to rule out that it is a general problem, I used an Android Studio template and created a simple sample app, added a customMyApplication
to the manifest and confirmed thatDecoroutinatorRuntime.load()
is not throwing.To compare the initialization process of the two apps (the working and the not working one) I replaced the call to
DecoroutinatorRuntime.load()
witherror("Error message")
. It looks like it's exactly the same:I noticed that the callstacks then load pretty identical:
Simple Sample App (Decoroutinator working)
my real app (Decoroutinator not working)
Any ideas how I can find out what is causing this or how to fix this? I could imagine that some part of the app is doing some static initialization and is using Coroutines there. But since it is a huge codebase, I don't have a clue how I could start investigating on that -- exchanging the ClassLoader and setting a breakpoint has the same issue: it's already too late.