[firebase_remote_config]: Returns empty on iPhone 17 Pro (iOS 26)

[ftl-huongdv]

Is there an existing issue for this?

• [x] I have searched the existing issues.

Which plugins are affected?

Remote Config

Which platforms are affected?

iOS

Description

Firebase Remote Config returns empty values only on iPhone 17 Pro (iOS 26). All older iPhones (iPhone 16 and earlier) work normally.

fetchAndActivate() completes successfully and does not throw any error, but all keys return empty strings on iPhone 17.

Reproducing the issue

install to iPhone 17 from TestFlight

Call: await Firebase.initializeApp(); try { await FirebaseRemoteConfig.instance.setConfigSettings( RemoteConfigSettings( fetchTimeout: const Duration(seconds: 30), minimumFetchInterval: const Duration(hours: 0), ), ); await FirebaseRemoteConfig.instance.fetchAndActivate(); } catch (error, stack) { FirebaseCrashlytics.instance.recordError( error, stack, fatal: true, reason: 'Remote Config Init Failed', ); } final rc = FirebaseRemoteConfig.instance; await rc.fetchAndActivate(); print(rc.getString("my_key"));

Output = ""

Install the same build on iPhone 16 → works normally

Firebase Core version

4.2.1

Flutter Version

3.24.5

Flutter dependencies

firebase_core: ^4.2.1 firebase_remote_config: ^6.1.2 firebase_messaging: ^16.0.4 firebase_analytics: ^12.0.4 firebase_crashlytics: ^5.0.5

Additional context and comments

XCode Version 16.3 (16E140)

[SelaseKay]

Hi @ftl-huongdv, thanks for the report. What version of iOS does your iPhone 16 run? Are you able to reproduce this locally(running the app in debug mode on your device)?

[ftl-huongdv]

Hi @ftl-huongdv, thanks for the report. What version of iOS does your iPhone 16 run? Are you able to reproduce this locally(running the app in debug mode on your device)?

Hello @SelaseKay, thanks for the quick response.

My iPhone 16 is running an iOS version lower than SDK 26

For the iPhone 17 issue: I cannot reproduce it locally in debug because I don't have an iPhone 17 device available here

[SelaseKay]

Hi @ftl-huongdv, I'm unable to reproduce this issue on an iPhone 17 Pro simulator running iOS 26. This suggests its probably a device-specific issue. Without a reliable way to reproduce this, there's not much we can do on our end, unfortunately.

[huongrealest]

@SelaseKay thank for update Today i just observed another case on a physical iPhone 13 Pro Max, also running iOS 26. Given this and the previous report, I believe the issue only occurs on physical devices and specifically on iOS 26. Just wanted to provide this additional update.

[google-oss-bot]

Hey @ftl-huongdv. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!