Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal Exception: kotlin.UninitializedPropertyAccessException #37

Open
vietmobilefolk opened this issue Aug 15, 2022 · 7 comments
Open

Comments

@vietmobilefolk
Copy link

vietmobilefolk commented Aug 15, 2022

I faced this issue when using react-native-track-player, which is utilizing KotlinAudio library:
Version: v0.1.34

Fatal Exception: kotlin.UninitializedPropertyAccessException: lateinit property descriptionAdapter has not been initialized
       at com.doublesymmetry.kotlinaudio.notification.NotificationManager$destroy$1.invokeSuspend(NotificationManager.kt:295)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:247)
       at android.app.ActivityThread.main(ActivityThread.java:8676)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)
@CDBridger
Copy link

yeah this is been in quite a few versions of it. Could we get a fix please?

@mpivchev
Copy link
Contributor

Please describe the steps you did that lead to the crash. Can you reproduce this in the example app?

@vietmobilefolk
Copy link
Author

vietmobilefolk commented Aug 17, 2022

@mpivchev
Although we occasionally experience it, it is reported in Crashlytics even though we can't always reproduce it in the example or our app. Although there aren't many users yet, incidents happen frequently.
Just curious as to why we don't confirm that the descriptionAdapter is initialized before calling its function.

@vietmobilefolk
Copy link
Author

Another observation concerning this problem is that it occurs when the app is running in the background.

@mpivchev
Copy link
Contributor

Just curious as to why we don't confirm that the descriptionAdapter is initialized before calling its function.

That's definitely something we can do

@s123121
Copy link

s123121 commented Sep 1, 2022

Can confirm, happen 100% whenever users put app in background (with another headless task registered)

@dcvz
Copy link
Contributor

dcvz commented Feb 6, 2024

Is this issue still present for users?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

5 participants