Firebase-android-sdk: W/zze: Application name is not set. Call Builder#setApplicationName.

[shadowsheep1]

What's this warning for?

W/zze: Application name is not set. Call Builder#setApplicationName.

I get it while calling

FirebaseRemoteConfig remoteConfig = FirebaseRemoteConfig.getInstance();

These my Firebase lib versions

implementation 'com.google.firebase:firebase-core:16.0.7'
implementation 'com.google.firebase:firebase-messaging:17.3.4'
implementation 'com.google.firebase:firebase-config:16.3.0'

There is also a SO question here.

[dirkam]

Same happens when using the new 16.4.0 version.

[samtstern]

This warning comes from AbstractGoogleClient in the Google APIs Java library but I don't see why Remote Config would be using that...

[dirkam]

@samtstern
16.3.0 switched to REST API, can it be the reason?

The Firebase Remote Config SDK requires the Firebase Remote Config REST API. For Firebase projects created before March 7, 2018, you must manually enable the REST API. For more information, see our Remote Config REST API user guide.

[rinlv]

Does anyone have a solution? @shadowsheep1 @dirkam @samtstern

[shadowsheep1]

@rinlv Nope, no solution. But apart from the warning all works fine on my side.

[sixpi]

I'm still seeing this in version 17.0.0, its cluttering up our log messages so a solution would be great. I can't find any function named setApplicationName in the firebase SDK for Android.

[sixpi]

Any updates?

[matzesoft]

I'm also passing the exact same issue with @flutter. Have anyone worked out a solution?

[leorachit]

Any solution for this?

[Josearias2703]

Same issue :c

[bubbleguuum]

Same here although it does not seem to have any side effect.

[gongelosP]

Any news on this issue ?

[Fernandomr88]

up

[sceee]

Also started for me popping up once FirebaseRemoteConfig was added.

[yjaquinas]

no solution yet :(

[bhanuka96]

this is working for me.

this is Dart language

adding await remoteConfig.fetch(expiration: const Duration(seconds: 0)); and await remoteConfig.activateFetched();

  void _adminValidate() async {
    try{
      final RemoteConfig remoteConfig = await RemoteConfig.instance;
      await remoteConfig.fetch(expiration: const Duration(seconds: 0));
      await remoteConfig.activateFetched();
      print(remoteConfig.getString('admin'));
    }catch (e){
      print(e);
    }
  }

[bubbleguuum]

This benign warning has disappeared since upgrading to firebase-config 19.0.2

[shadowsheep1]

@bubbleguuum You're right! It seems so.