setURLStreamHandlerFactory is incompatible with Firebase
Closed this issue · 3 comments
yschimke commented
W It's not necessary to set Accept-Encoding on requests - cronet will do this automatically for you, and setting it yourself has no effect. See https://crbug.com/581399 for details.
java.lang.Exception
at m.iv.b(:com.google.android.gms.dynamite_cronetdynamite@234412038@23.44.12 (190400-0):18)
at m.iv.addHeader(:com.google.android.gms.dynamite_cronetdynamite@234412038@23.44.12 (190400-0):1)
at m.jn.l(:com.google.android.gms.dynamite_cronetdynamite@234412038@23.44.12 (190400-0):149)
at m.jn.j(:com.google.android.gms.dynamite_cronetdynamite@234412038@23.44.12 (190400-0):23)
at m.jn.getResponseCode(:com.google.android.gms.dynamite_cronetdynamite@234412038@23.44.12 (190400-0):1)
at com.google.android.datatransport.cct.CctTransportBackend.doSend(CctTransportBackend.java:317)
at com.google.android.datatransport.cct.CctTransportBackend.$r8$lambda$bLAzIpNF4NtapXlUpPVGhzxyNT8(Unknown Source:0)
at com.google.android.datatransport.cct.CctTransportBackend$$ExternalSyntheticLambda0.apply(Unknown Source:4)
at com.google.android.datatransport.runtime.retries.Retries.retry(Retries.java:54)
at com.google.android.datatransport.cct.CctTransportBackend.send(CctTransportBackend.java:372)
at com.google.android.datatransport.runtime.scheduling.jobscheduling.Uploader.logAndUpdateState(Uploader.java:146)
at com.google.android.datatransport.runtime.scheduling.jobscheduling.Uploader.lambda$upload$1$com-google-android-datatransport-runtime-scheduling-jobscheduling-Uploader(Uploader.java:105)
at com.google.android.datatransport.runtime.scheduling.jobscheduling.Uploader$$ExternalSyntheticLambda2.run(Unknown Source:8)
at com.google.android.datatransport.runtime.SafeLoggingExecutor$SafeLoggingRunnable.run(SafeLoggingExecutor.java:47)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
I'm using 0.1.0, and not intending to set it.
Example request Making request to: https://firebaselogging-pa.googleapis.com/v1/firelog/legacy/batchlog
yschimke commented
Going to close, I suspect this is either on an image loading library. Or through firebase.
yschimke commented
I realise this is not really an issue with the bridge, but might be useful if the bridge disabled this warning, or removed in the interceptor? Very spammy otherwise.
colibie commented
Reduced the log level of the header warning. Available from Cronet M126.