We were happy with v2, but there were several weird crashes that weĪfter reading the instructions, the update process went super smooth. We've had a lot of work coming in, and we haven't been able to update it to We've been using Mosby for a fair amount of time on a production app.
Steps to reproduce the behavior or link to a sample repositoryĪdd any MvpViewGroup class to the WindowManager (using the SYSTEM_ALERT_WINDOW permission) : Could not find the surrounding ActivityĪt 圓.PresenterManager.getActivity(PresenterManager.java:229)Īt 圓.(ViewGroupMvpDelegateImpl.java:79)Īt 圓.(MvpRelativeLayout.java:77)Īt 圓.(MvpRelativeLayout.java:85)Īt XXXX.onAttachedToWindow(WidgetContainer.kt:107)Īt (View.java:17377)Īt (ViewGroup.java:3319)Īt (ViewRootImpl.java:1658)Īt (ViewRootImpl.java:1386)Īt $n(ViewRootImpl.java:6733)Īt $n(Choreographer.java:911)Īt (Choreographer.java:723)Īt (Choreographer.java:658)Īt $n(Choreographer.java:897)Īt android.os.Handler.handleCallback(Handler.java:789)Īt android.os.Handler.dispatchMessage(Handler.java:98)Īt android.os.Looper.loop(Looper.java:164)Īt (ActivityThread.java:6541)Īt .invoke(Native Method)Īt .Zygote$n(Zygote.java:240)Īt .ZygoteInit.main(ZygoteInit.java:767) If you want to me to assemble a little project with the parts that would reproduce the issue, don't doubt to askĪctual behavior (include a stacktrace if crash)ġ1-22 23:58:49.622 17039-17039/? E/AndroidRuntime: FATAL EXCEPTION: main The context you can retrieve there, is directly the Application object, so it is impossible to cast it to Activity. When the views are attached to the window, the PresenterManager class tries to obtain the Activity, with no success. For example, our root view inherits from MvpRelativeLayout.
Our app is using the WindowManager to show contextual info when you are outside of the app. All the views that we've been using on the app were correctly rendered. We were happy with v2, but there were several weird crashes that we wanted to solve.Īfter reading the instructions, the update process went super smooth. We've had a lot of work coming in, and we haven't been able to update it to the v3.
0 kommentar(er)
