Remote Config throws NetworkOnMainThreadException on Android 6 (API 23) - v33.13.0

[brunopiovan]

Just do the basic implementation of Remote Config using bom v33.13.0 on API 23, open the app and put it on background.

I'm getting tons of the error below, only on Android 6:

Fatal Exception: android.os.NetworkOnMainThreadException: at android.os.StrictMode$AndroidBlockGuardPolicy.onNetwork(StrictMode.java:1332) at com.android.org.conscrypt.Platform.blockGuardOnNetwork(Platform.java:300) at com.android.org.conscrypt.OpenSSLSocketImpl.shutdownAndFreeSslNative(OpenSSLSocketImpl.java:1217) at com.android.org.conscrypt.OpenSSLSocketImpl.close(OpenSSLSocketImpl.java:1212) at com.android.okhttp.Connection.closeIfOwnedBy(Connection.java:173) at com.android.okhttp.OkHttpClient$1.closeIfOwnedBy(OkHttpClient.java:77) at com.android.okhttp.internal.http.HttpConnection.closeIfOwnedBy(HttpConnection.java:137) at com.android.okhttp.internal.http.HttpTransport.disconnect(HttpTransport.java:135) at com.android.okhttp.internal.http.HttpEngine.disconnect(HttpEngine.java:600) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.disconnect(HttpURLConnectionImpl.java:134) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.disconnect(DelegatingHttpsURLConnection.java:93) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.disconnect(HttpsURLConnectionImpl.java) at com.google.firebase.remoteconfig.internal.ConfigRealtimeHttpClient.setIsInBackground(ConfigRealtimeHttpClient.java:413) at com.google.firebase.remoteconfig.internal.ConfigRealtimeHandler.setBackgroundState(ConfigRealtimeHandler.java:94) at com.google.firebase.remoteconfig.FirebaseRemoteConfig.setConfigUpdateBackgroundState(FirebaseRemoteConfig.java:715) at com.google.firebase.remoteconfig.RemoteConfigComponent.notifyRCInstances(RemoteConfigComponent.java:367) at com.google.firebase.remoteconfig.RemoteConfigComponent.access$100(RemoteConfigComponent.java:64) at com.google.firebase.remoteconfig.RemoteConfigComponent$GlobalBackgroundListener.onBackgroundStateChanged(RemoteConfigComponent.java:405) at com.google.android.gms.common.api.internal.BackgroundDetector.zza(com.google.android.gms:play-services-basement@@18.5.0:3) at com.google.android.gms.common.api.internal.BackgroundDetector.onTrimMemory(com.google.android.gms:play-services-basement@@18.5.0:3) at android.app.Application.onTrimMemory(Application.java:136) at android.app.ActivityThread.handleTrimMemory(ActivityThread.java:5188) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1755) at android.os.Handler.dispatchMessage(Handler.java:110) at android.os.Looper.loop(Looper.java:203) at android.app.ActivityThread.main(ActivityThread.java:6339) at java.lang.reflect.Method.invoke(Method.java) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1084) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:945)

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[technicalflaw]

I'm noticing this as well, except so far 100% Android 7, with the same stack trace.

I presume it's related to the "Fixed an issue where the connection to the real-time Remote Config backend could remain open in the background." fix in the latest BOM (Remote Config v22.1.1).

[brunopiovan]

I presume it's related to the "Fixed an issue where the connection to the real-time Remote Config backend could remain open in the background." fix in the latest BOM (Remote Config v22.1.1).

Agree!

[lehcar09]

Hi folks, thank you for raising the issue. I tried reproducing this issue on Android 6 and 7 emulators, but I did not encounter the error. Our engineers are looking into it. We'll get back to you as soon as we have updates. Thanks!

[tusharkhandelwal8]

Hi, we were able to reproduce this issue on Android 6 and 7 emulators. The fix for this issue has now been merged, and you will be able to see the change in the next release. Thanks.

[tusharkhandelwal8]

Fix: #6940

[SimonMarquis]

@tusharkhandelwal8 does that mean the fixed issue in 22.1.1 (where the connection to the real-time Remote Config backend could remain open in the background) will re-surface on API levels before 26?
Has the option to switching thread before calling httpURLConnection.disconnect() been considered?

[tusharkhandelwal8]

Yes, we did consider the option of switching threads before calling httpURLConnection.disconnect(). However, as this problem is specific to the OS implementation on very old versions, affecting less than 0.5% of users, a version-specific change appears to be the most practical solution for now. Even for API levels before 26 the connection won't remain open forever it will automatically close after 4 minutes as we used to see earlier.