[firebase_remote_config]: RCN Fetch failure: Error Domain=NSURLErrorDomain on 18.4 simulator

[marclester-tang]

Is there an existing issue for this?

• I have searched the existing issues.

Which plugins are affected?

Remote Config

Which platforms are affected?

iOS

Description

This issue appears similar to or the same as the one reported in #14728.

Steps to reproduce:

1. Ensure Firebase Remote Config is integrated and configured in an iOS application.
2. Run the application and allow Remote Config to attempt a fetch.
3. Terminate the application completely.
4. Relaunch the application.
5. Observe the console logs for the described "cannot parse response" error during the initial Remote Config fetch attempt after restart.

Observed behavior:

• Upon application restart, the Firebase Remote Config fetch operation fails with the error Error Domain=NSURLErrorDomain Code=-1017 "cannot parse response".
• The logs indicate "No cached config result", suggesting that the fetch failure prevents the SDK from loading previously cached values.

Expected behavior:

• Firebase Remote Config should successfully fetch the latest configuration from the backend.
• If the fetch fails, the SDK should gracefully handle the error and ideally load a cached version of the configuration if available.

Firebase SDK Version:

11.10.0 (as indicated in the provided logs)

Xcode Version:

16.3

Installation Method:

Flutter installation

Firebase Product(s):

Remote Config Simulator 18.4

Targeted Platforms:

iOS

Relevant Log Output:

(Included in the description above)

Additional context:

This issue seems highly related to #14728. It would be helpful to understand if the fix mentioned in that issue has been released and if there are any specific steps required to ensure it is integrated correctly, or if this is a recurring problem.

Reproducing the issue

1. Ensure Firebase Remote Config is integrated and configured in an iOS application.
2. Run the application and allow Remote Config to attempt a fetch.
3. Terminate the application completely.
4. Relaunch the application.
5. Observe the console logs for the described "cannot parse response" error during the initial Remote Config fetch attempt after restart.

Firebase Core version

3.13.0

Flutter Version

3.29.3

Relevant Log Output

11.10.0 - [FirebaseRemoteConfig][I-RCN000026] RCN Fetch failure: Error Domain=NSURLErrorDomain Code=-1017 "cannot parse response" UserInfo={_kCFStreamErrorCodeKey=-1, NSUnderlyingError=0x600000c91a70 {Error Domain=kCFErrorDomainCFNetwork Code=-1017 "(null)" UserInfo={NSErrorPeerAddressKey=<CFData 0x60000214ba70 [0x1e6ebb4f0]>{length = 16, capacity = 16, bytes = 0x100201bb8efbdcea0000000000000000}, _kCFStreamErrorCodeKey=-1, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <0D7410F8-8259-467F-82D8-B7A9E85B8AD3>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDataTask <0D7410F8-8259-467F-82D8-B7A9E85B8AD3>.<1>"
), NSLocalizedDescription=cannot parse response, NSErrorFailingURLStringKey=https://firebaseremoteconfig.googleapis.com/v1/projects/shopsm-v5/namespaces/firebase:fetch?key=AIzaSyBKRVyGM79C-Q9fVrld01cbPAF1N0hU4oI, NSErrorFailingURLKey=https://firebaseremoteconfig.googleapis.com/v1/projects/shopsm-v5/namespaces/firebase:fetch?key=AIzaSyBKRVyGM79C-Q9fVrld01cbPAF1N0hU4oI, _kCFStreamErrorDomainKey=4}. No cached config result.

Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments

No response

[SelaseKay]

Hi @marclester-tang, this seems to be a duplicate of #17349.