adyen-android: Uninitialized lateinit property
Describe the bug
The lateinit
property BaseComponentDialogFragment#component
is not initialized when used by GenericComponentDialogFragment
.
To Reproduce I haven’t been able to reproduce the crash. I have tried forcing screen restorations using the “Discard Activities” toggle, but haven’t been able to successfully reproduce it.
Expected behavior The property should be initialized before use
Smartphone (please complete the following information):
- Device: HUAWEI P smart 2019
- OS: Android 10
- Browser: N.A. Don’t have access to this info in our crash logs
- Version: (Adyen version): 4.1.1
Additional context StackTrace:
Fatal Exception: kotlin.UninitializedPropertyAccessException lateinit property component has not been initialized
com.adyen.checkout.dropin.ui.base.BaseComponentDialogFragment.getComponent (BaseComponentDialogFragment.java:50)
com.adyen.checkout.dropin.ui.component.GenericComponentDialogFragment.onViewCreated (GenericComponentDialogFragment.java:70)
androidx.fragment.app.Fragment.performViewCreated (Fragment.java:2987)
androidx.fragment.app.FragmentStateManager.createView (FragmentStateManager.java:546)
androidx.fragment.app.FragmentStateManager.moveToExpectedState (FragmentStateManager.java:282)
androidx.fragment.app.FragmentManager.executeOpsTogether (FragmentManager.java:2189)
androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute (FragmentManager.java:2100)
androidx.fragment.app.FragmentManager.execPendingActions (FragmentManager.java:2002)
androidx.fragment.app.FragmentManager$5.run (FragmentManager.java:524)
android.os.Handler.handleCallback (Handler.java:888)
android.os.Handler.dispatchMessage (Handler.java:100)
android.os.Looper.loop (Looper.java:213)
android.app.ActivityThread.main (ActivityThread.java:8178)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:513)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1101)
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 18
@santiJourni we just released 4.2.0 which includes the fix for this issue, it should be live in maven central a bit. If you upgrade to this version you can remove the
BcmcConfiguration
workaround 😄