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

TransactionPayloadFragment.kt line 102 error #935

Open
jDilshodbek opened this issue Dec 7, 2022 · 5 comments
Open

TransactionPayloadFragment.kt line 102 error #935

jDilshodbek opened this issue Dec 7, 2022 · 5 comments
Labels
incomplete This issue needs more data in order to be triaged

Comments

@jDilshodbek
Copy link

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object kotlin.Pair.component1()' on a null object reference

   at com.chuckerteam.chucker.internal.ui.transaction.TransactionPayloadFragment.onViewCreated$lambda-2(TransactionPayloadFragment.kt:102)
   at com.chuckerteam.chucker.internal.ui.transaction.TransactionPayloadFragment.$r8$lambda$T903xsqZYw_77gb8vnhfSzuuVAk()
   at com.chuckerteam.chucker.internal.ui.transaction.TransactionPayloadFragment$$ExternalSyntheticLambda1.onChanged(:4)
   at androidx.lifecycle.LiveData.considerNotify(LiveData.java:133)
   at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:151)
   at androidx.lifecycle.LiveData.setValue(LiveData.java:309)
   at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50)
   at com.chuckerteam.chucker.internal.support.LiveDataUtilsKt.combineLatest$lambda-2$lambda-0(LiveDataUtils.kt:21)
   at com.chuckerteam.chucker.internal.support.LiveDataUtilsKt.$r8$lambda$mOyt4m3D7rz_Sl6O-_wkqyiVEGQ()
   at com.chuckerteam.chucker.internal.support.LiveDataUtilsKt$$ExternalSyntheticLambda2.onChanged(:8)
   at androidx.lifecycle.MediatorLiveData$Source.onChanged(MediatorLiveData.java:155)
   at androidx.lifecycle.LiveData.considerNotify(LiveData.java:133)
   at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:151)
   at androidx.lifecycle.LiveData.setValue(LiveData.java:309)
   at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50)
   at androidx.lifecycle.LiveData$1.run(LiveData.java:93)
   at android.os.Handler.handleCallback(Handler.java:873)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at android.os.Looper.loop(Looper.java:193)
   at android.app.ActivityThread.main(ActivityThread.java:6762)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
@vbuberen
Copy link
Collaborator

vbuberen commented Dec 7, 2022

Please provide data according to the template provided to you while opening the issue.

@vbuberen vbuberen added the incomplete This issue needs more data in order to be triaged label Dec 7, 2022
@jDilshodbek
Copy link
Author

Please provide data according to the template provided to you while opening the issue.

I have recently added chucker library into my project with
implementation "com.github.chuckerteam.chucker:library:3.5.2"
and my chukcer setup inside okhttpClient
val chuckerCollector = ChuckerCollector( context = MyApp.context, showNotification = true, retentionPeriod = RetentionManager.Period.ONE_HOUR ) @Suppress("MagicNumber") val chuckerInterceptor = ChuckerInterceptor.Builder(MyTaxiDriver.context) .collector(chuckerCollector) .maxContentLength(250_000L) .redactHeaders(emptySet()) .alwaysReadResponseBody(false) .build() builder.addInterceptor(chuckerInterceptor)

and I got this crash report from Firebase reports

@cortinico
Copy link
Member

and I got this crash report from Firebase reports

You should not be shipping Chucker in production releases, that's why we have the -no-op artifact. Why are you getting crash reports on Firebase for it?

@jDilshodbek
Copy link
Author

and I got this crash report from Firebase reports

You should not be shipping Chucker in production releases, that's why we have the -no-op artifact. Why are you getting crash reports on Firebase for it?

We test network requests in production environment if they are working properly

@cortinico
Copy link
Member

We test network requests in production environment if they are working properly

Sorry but I don't understand this statement. Your final users will be able to open Chucker (which is a debug tool) if you ship it in production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete This issue needs more data in order to be triaged
Projects
None yet
Development

No branches or pull requests

3 participants