Plugin(s): "@capacitor-firebase/authentication": "^0.5.0"

Platform(s): Android

Current behavior: When using const result = await FirebaseAuthentication.signInWithGoogle() for example, the login is successful and result.user is returned. However, authStateChange is never fired. Note that this works in web, but NOT on Android.

Expected behavior: authStateChange needs to be fired on any change in auth state, e.g. re-opening app or signing out.

Steps to reproduce:

Related code:

  // capacitor.config.json
  "plugins": {
    "FirebaseAuthentication": {
      "skipNativeAuth": false,
      "providers": ["twitter.com", "google.com", "facebook.com"]
    },
  }

// main.ts
import { FirebaseAuthentication } from "@capacitor-firebase/authentication";
FirebaseAuthentication.removeAllListeners().then(() => {
  FirebaseAuthentication.addListener("authStateChange", (result) => {
    if (result.user) {
      // this never fires
    } else {
      // this never fires
    }
  });
});

  // Login.vue
  const signInWithGoogle = async () => {
    try {
      const result: SignInResult = await FirebaseAuthentication.signInWithGoogle();

      if (result.user) {
        return result.user;
      }
    } catch (err) {
      console.log(err);
    }
  };

Other information: Some potentially relevant logs from Android Studio:

V/Capacitor/FirebaseAuthenticationPlugin: Notifying listeners for event authStateChange D/Capacitor/FirebaseAuthenticationPlugin: No listeners found for event authStateChange V/Capacitor/Plugin: To native (Capacitor plugin): callbackId: 81763094, pluginId: FirebaseAuthentication, methodName: addListener V/Capacitor: callback: 81763094, pluginId: FirebaseAuthentication, methodName: addListener, methodData: {"eventName":"authStateChange"}

Also, it looks like there's a similar issue that was closed but with no real solution, https://github.com/capawesome-team/capacitor-firebase/issues/56

Capacitor doctor:

Latest Dependencies:

  @capacitor/cli: 3.6.0
  @capacitor/core: 3.6.0
  @capacitor/android: 3.6.0
  @capacitor/ios: 3.6.0

Installed Dependencies:

  @capacitor/cli: 3.4.3
  @capacitor/core: 3.4.3
  @capacitor/android: 3.4.3
  @capacitor/ios: 3.4.3

Plugin(s):

Analytics

Platform(s):

iOS

Current behavior:

I added the Analytics plugin as per instructions. However when I try to build the iOS app, it fails with "No such module FirebaseCore". Could somebody please help? Production app needing an update.....

Expected behavior:

Xcode should build successfully

Steps to reproduce:

Related code:

insert short code snippets here

Other information:

Capacitor doctor:

💊   Capacitor Doctor  💊 

Latest Dependencies:

  @capacitor/cli: 4.1.0
  @capacitor/core: 4.1.0
  @capacitor/android: 4.1.0
  @capacitor/ios: 4.1.0

Installed Dependencies:

  @capacitor/cli: 4.0.1
  @capacitor/core: 4.1.0
  @capacitor/android: 4.1.0
  @capacitor/ios: 4.1.0

[success] iOS looking great! 👌
[success] Android looking great! 👌

Pull request checklist

Please check if your PR fulfills the following requirements:

• [x] The changes have been tested successfully.
• [x] A changeset has been created (npm run changeset).

Close #35

Plugin(s): Capacitor Firebase Authentication

Platform(s): IOS fails but web works fine

Current behavior: When I use this plugin and console log results, the web version works fine. When I attempt to use the similar logging for Native Platform (Confirming that the Native code is working) trying the addListener command in several locations (see Github Repo) on the IOS logging does not seem to be firing

Expected behavior: What I am wanting to achive is to get Firebase Custom Claims and report them (and then perform access actions based on those claims)

Steps to reproduce: See Git Repo - comment with logic with various positions of the addListener

Related code: https://github.com/sclawer/MobileApp

Other information:

Capacitor doctor:

💊   Capacitor Doctor  💊 

Latest Dependencies:

  @capacitor/cli: 3.4.3
  @capacitor/core: 3.4.3
  @capacitor/android: 3.4.3
  @capacitor/ios: 3.4.3

Installed Dependencies:

  @capacitor/cli: 3.4.3
  @capacitor/core: 3.4.3
  @capacitor/android: 3.4.3
  @capacitor/ios: 3.4.3

[success] iOS looking great! 👌
[success] Android looking great! 👌

Pull request checklist

Please check if your PR fulfills the following requirements:

• [x] The changes have been tested successfully.
• [x] A changeset has been created (npm run changeset).

Implements #36

Plugin(s):

• @capacitor-firebase/[email protected]

Platform(s):

• ios

Current behavior: I added the plugin to my capacitor app, set up push notifications and background modes. Added snippets as described to AppDelegate.swift and FirebaseAppDelegateProxyEnabled to Info.plist. Also added GoogleService-Info.plist to the xcode project.

After building and running the app on a mobile device, I see these errors in xcode logs:

[FirebaseCore][I-COR000003] The default Firebase app has not yet been configured. Add `FirebaseApp.configure()` to your application initialization. This can be done in in the App Delegate's application(_:didFinishLaunchingWithOptions:)` (or the `@main` struct's initializer in SwiftUI).

[FirebaseMessaging][I-FCM002023] The object <CapacitorFirebaseMessaging.FirebaseMessaging: 0x282da5380> does not respond to -messaging:didReceiveRegistrationToken:. Please implement -messaging:didReceiveRegistrationToken: to be provided with an FCM token.

Expected behavior: No warnings of uninitialized Firebase components in xcode log.

Steps to reproduce: build and run the app.

Related code:

Other information:

Capacitor doctor:

💊   Capacitor Doctor  💊 

Latest Dependencies:

  @capacitor/cli: 3.6.0
  @capacitor/core: 3.6.0
  @capacitor/android: 3.6.0
  @capacitor/ios: 3.6.0

Installed Dependencies:

  @capacitor/cli: 3.5.1
  @capacitor/core: 3.6.0
  @capacitor/android: 3.6.0
  @capacitor/ios: 3.6.0

[success] iOS looking great! 👌
[success] Android looking great! 👌

Hi,

I can see an issue with your demo app. The below method doesn't fire on Log out and open the app from App Kill use cases. Any clue? Thanks!

I have used it like so:

firebase-authentication.service.ts

 setFirebaseAuthStateChange(): void {
   FirebaseAuthentication.removeAllListeners().then(() => {
      FirebaseAuthentication.addListener('authStateChange', (change) => {
        this.ngZone.run(() => {
          this.authStateSubj.next(change);
        });
      });
    });
}

app. componnet.ts

  ngOnInit(): void {
    this.initializeApp();
  }

 private initializeApp(): void {
     this.firebaseAuthenticationService.setFirebaseAuthStateChange();
 }

It works only when the Login use case. I have used AngularFire on many applications and below works on all the above use cases. So we would like to have the same behavior also on your plugin too. Please let me know your thoughts here.

this.angularFireAuth.authState.subscribe(async (user: firebase.default.User) => {
 
    });

Ionic:

   Ionic CLI                     : 6.16.3 (C:\Users\Sampath\AppData\Roaming\npm\node_modules\@ionic\cli)
   Ionic Framework               : @ionic/angular 6.0.11
   @angular-devkit/build-angular : 13.0.1
   @angular-devkit/schematics    : 13.0.1
   @angular/cli                  : 13.0.1
   @ionic/angular-toolkit        : 5.0.0

Capacitor:

   Capacitor CLI      : 3.4.0
   @capacitor/android : 3.4.1
   @capacitor/core    : 3.4.0
   @capacitor/ios     : not installed

Utility:

   cordova-res : 0.15.3
   native-run  : 1.5.0

System:

   NodeJS : v14.16.1 (C:\Program Files\nodejs\node.exe)
   npm    : 6.14.12
   OS     : Windows 10

Is your feature request related to an issue? Please describe:

Yeah. In social media entries (Facebook, Google, GooglePlay, Twitter, Apple etc.), the user's id value connected to the provider does not appear. (GoogleId value does not come for login with Google.)

Describe your desired solution:

When the user logs in, the user's id value can be added according to the response that the provider returns. (I left a small demo below)

Describe the alternatives you are considering:

I mentioned it in the additional context section.

Additional context:

I have attached the codes to be edited. This is for android only. It works successfully when I tested it for Facebook, Google and Twitter.

Thanks for your time!

1. FirebaseAuthenticationHelper.java

// updated one function

// update params

    public static JSObject createSignInResult(FirebaseUser user, AuthCredential credential, String idToken, String id) {
        JSObject userResult = FirebaseAuthenticationHelper.createUserResult(user);
        JSObject credentialResult = FirebaseAuthenticationHelper.createCredentialResult(credential, idToken); // update call params
        JSObject result = new JSObject();
        
// add next line

       userResult.put("id", id); // add this line
        result.put("user", userResult);
        result.put("credential", credentialResult);
        return result;
    }

2. FirebaseAuthentication.java

// updated two functions

    public void signInWithCustomToken(PluginCall call) {
        boolean skipNativeAuth = this.config.getSkipNativeAuth();
        if (skipNativeAuth) {
            call.reject(ERROR_CUSTOM_TOKEN_SKIP_NATIVE_AUTH);
            return;
        }

        String token = call.getString("token", "");

        firebaseAuthInstance
            .signInWithCustomToken(token)
            .addOnCompleteListener(
                plugin.getActivity(),
                new OnCompleteListener<AuthResult>() {
                    @Override
                    public void onComplete(@NonNull Task<AuthResult> task) {
                        if (task.isSuccessful()) {
                            Log.d(FirebaseAuthenticationPlugin.TAG, "signInWithCustomToken succeeded.");
                            FirebaseUser user = getCurrentUser();

// updated next line

JSObject signInResult = FirebaseAuthenticationHelper.createSignInResult(user, null, null, null); // update call params
                            call.resolve(signInResult);
                        } else {
                            Log.e(FirebaseAuthenticationPlugin.TAG, "signInWithCustomToken failed.", task.getException());
                            call.reject(ERROR_SIGN_IN_FAILED);
                        }
                    }
                }
            )
            .addOnFailureListener(
                plugin.getActivity(),
                new OnFailureListener() {
                    @Override
                    public void onFailure(@NonNull Exception) {
                        Log.e(FirebaseAuthenticationPlugin.TAG, "signInWithCustomToken failed.", exception);
                        call.reject(ERROR_SIGN_IN_FAILED);
                    }
                }
            );
    }

// 1. update params    

public void handleSuccessfulSignIn(final PluginCall call, AuthCredential credential, String idToken, String id) {
        boolean skipNativeAuth = this.config.getSkipNativeAuth();
        if (skipNativeAuth) {

// 2. update call params

            JSObject signInResult = FirebaseAuthenticationHelper.createSignInResult(null, credential, idToken, id); // update call params
            call.resolve(signInResult);
            return;
        }
        firebaseAuthInstance
            .signInWithCredential(credential)
            .addOnCompleteListener(
                plugin.getActivity(),
                new OnCompleteListener<AuthResult>() {
                    @Override
                    public void onComplete(@NonNull Task<AuthResult> task) {
                        if (task.isSuccessful()) {
                            Log.d(FirebaseAuthenticationPlugin.TAG, "signInWithCredential succeeded.");
                            FirebaseUser user = getCurrentUser();

// 3. update call params

                            JSObject signInResult = FirebaseAuthenticationHelper.createSignInResult(user, credential, idToken, id); // update call params
                            call.resolve(signInResult);
                        } else {
                            Log.e(FirebaseAuthenticationPlugin.TAG, "signInWithCredential failed.", task.getException());
                            call.reject(ERROR_SIGN_IN_FAILED);
                        }
                    }
                }
            )
            .addOnFailureListener(
                plugin.getActivity(),
                new OnFailureListener() {
                    @Override
                    public void onFailure(@NonNull Exception exception) {
                        Log.e(FirebaseAuthenticationPlugin.TAG, "signInWithCredential failed.", exception);
                        call.reject(ERROR_SIGN_IN_FAILED);
                    }
                }
            );
    }

3. handlers/PlayGamesAuthProviderHandler.java

update one Function

    public void handleOnActivityResult(PluginCall call, ActivityResult result) {
        Intent data = result.getData();
        Task<GoogleSignInAccount> task = GoogleSignIn.getSignedInAccountFromIntent(data);
        try {
            GoogleSignInAccount account = task.getResult(ApiException.class);
            String serverAuthCode = account.getServerAuthCode();
            AuthCredential credential = PlayGamesAuthProvider.getCredential(serverAuthCode);
            String idToken = account.getIdToken();
            String id = account.getId(); // add this and update call from next line
            pluginImplementation.handleSuccessfulSignIn(call, credential, idToken, id); // update call params
        } catch (ApiException exception) {
            pluginImplementation.handleFailedSignIn(call, null, exception);
        }
    }

4. handlers/PhoneAuthProviderHandler

// updated three functions

    private void handleVerificationCode(PluginCall call, String verificationId, String verificationCode) {
        PhoneAuthCredential credential = PhoneAuthProvider.getCredential(verificationId, verificationCode);

// update call params from next line

        pluginImplementation.handleSuccessfulSignIn(call, credential, null, null); // update call params
    }

            @Override
            public void onVerificationCompleted(PhoneAuthCredential credential) {

// update call params from next line

                pluginImplementation.handleSuccessfulSignIn(call, credential, null, null); // update call params
            }

            @Override
            public void onCodeSent(@NonNull String verificationId, @NonNull PhoneAuthProvider.ForceResendingToken token) {

// update call params from next line             

   JSObject result = FirebaseAuthenticationHelper.createSignInResult(null, null, null, null); // update call params
                result.put("verificationId", verificationId);
                call.resolve(result);
            }

5. handlers/OAuthProviderHandler

// update two functions

    private void startActivityForSignIn(final PluginCall call, OAuthProvider.Builder provider) {
        pluginImplementation
            .getFirebaseAuthInstance()
            .startActivityForSignInWithProvider(pluginImplementation.getPlugin().getActivity(), provider.build())
            .addOnSuccessListener(
                authResult -> {
                    AuthCredential credential = authResult.getCredential();
                    
// add next line and update call params

Object userId = authResult.getAdditionalUserInfo().getProfile().get("id");
                    pluginImplementation.handleSuccessfulSignIn(call, credential, null, userId.toString()); // update call params
                }
            )
            .addOnFailureListener(exception -> pluginImplementation.handleFailedSignIn(call, null, exception));
    }

    private void finishActivityForSignIn(final PluginCall call, Task<AuthResult> pendingResultTask) {
        pendingResultTask
            .addOnSuccessListener(
                authResult -> {
                    AuthCredential credential = authResult.getCredential();
                    
// add next line and update call params

Object userId = authResult.getAdditionalUserInfo().getProfile().get("id");
                    pluginImplementation.handleSuccessfulSignIn(call, credential, null,  userId.toString()); // update call params
                }
            )
            .addOnFailureListener(exception -> pluginImplementation.handleFailedSignIn(call, null, exception));
    }

6. handlers/GoogleAuthProviderHandler

update one function

    public void handleOnActivityResult(PluginCall call, ActivityResult result) {
        Intent data = result.getData();
        Task<GoogleSignInAccount> task = GoogleSignIn.getSignedInAccountFromIntent(data);
        try {
            GoogleSignInAccount account = task.getResult(ApiException.class);
            String idToken = account.getIdToken();

// add next line and update call params

            String id = account.getId();
            AuthCredential credential = GoogleAuthProvider.getCredential(idToken, null);
            pluginImplementation.handleSuccessfulSignIn(call, credential, idToken, id); // update call params
        } catch (ApiException exception) {
            pluginImplementation.handleFailedSignIn(call, null, exception);
        }
    }

7. handlers/FacebookAuthProviderHandler

update one function

    private void handleSuccessCallback(LoginResult loginResult) {
        AccessToken accessToken = loginResult.getAccessToken();
        String token = accessToken.getToken();

// add next line and update call params     

   String id = accessToken.getUserId();
        AuthCredential credential = FacebookAuthProvider.getCredential(token);
        pluginImplementation.handleSuccessfulSignIn(savedCall, credential, token, id); // update call params
    }

Plugin(s): @capacitor-firebase/[email protected]

Platform(s): iOS

Current behavior: Twitter Auth Provider cannot transition from native auth to Firebase JS SDK auth. The FirebaseAuthentication.signInWithTwitter() method returns no result.credential.accessToken nor result.credential.secret (both undefined). Thus I'm unable to get the OAuthCredential using const nativeCredential = TwitterAuthProvider.credential(result.credential?.accessToken, result.credential?.secret) in order to perform the authentication on the web layer with signInWithCredential(auth, nativeCredential).

Expected behavior: Twitter auth provider returns credential.accessToken and credential.secret (like it does on Android) and we can use those to perform the authentication on the web layer with signInWithCredential(auth, nativeCredential).

Steps to reproduce: I followed the steps mentioned in the How to use this plugin with the Firebase JavaScript SDK guide.

Related code: But as the Twitter example is missing I used the following (based on the other examples)

const signInWithTwitter = async () => {
  // 1. Create credentials on the native layer
  const result = await FirebaseAuthentication.signInWithTwitter();
  // 2. Sign in on the web layer using the access token
  const credential = TwitterAuthProvider.credential(result.credential?.accessToken, result.credential?.secret);
  const auth = getAuth();
  await signInWithCredential(auth, credential);
};

Other information: My project is working fine on Android and the web. On iOS I got these errors on the Safari DevTools console:

• FirebaseError: Firebase: Error (auth/argument-error).
• null is not an object (evaluating 'credential._getIdTokenResponse')

This is the way I'm initializing the @angular/fire library in my NgModule according to this comment and this comment:

...

provideFirebaseApp(() => {
    const app = initializeApp(environment.firebase);

    if (Capacitor.isNativePlatform()) {
      initializeAuth(app, {
        persistence: indexedDBLocalPersistence
      });
    }
    return app;
  }),
  provideAuth(() => getAuth())

...

I also tried this alternate init with no luck. I don't believe this is the cause anyway:

provideFirebaseApp(() => initializeApp(environment.firebase)),
provideAuth(() => {
  if (Capacitor.isNativePlatform()) {
    return initializeAuth(getApp(), {
      persistence: indexedDBLocalPersistence
    });
  } else {
    return getAuth();
  }
}),

Capacitor doctor:

💊   Capacitor Doctor  💊 

Latest Dependencies:

  @capacitor/cli: 3.5.1
  @capacitor/core: 3.5.1
  @capacitor/android: 3.5.1
  @capacitor/ios: 3.5.1

Installed Dependencies:

  @capacitor/cli: 3.5.1
  @capacitor/ios: 3.5.1
  @capacitor/android: 3.5.1
  @capacitor/core: 3.5.1

[success] iOS looking great! 👌
[error] Missing <manifest package=""> attribute in app/src/main

Pull request checklist

Please check if your PR fulfills the following requirements:

• [x] The changes have been tested successfully.
• [x] A changeset has been created (npm run changeset).

Close #224

Plugin(s):

"@capacitor-firebase/app": "^1.0.0", "@capacitor-firebase/authentication": "^1.0.0",

Platform(s):

iOS

Current behavior:

When trying to signInWithGoogle the function runs but no pop up occurs and no data is being returned. To Native -> FirebaseAuthentication signInWithGoogle 60979170 is the message I get in the logs.

Expected behavior:

Assume a pop up should come up and ask me to sign in with google have tried same code and another plugin all works but wanted to use this plugin.

Steps to reproduce:

Install, setup the signInWithGoogle function and nothing happens

Related code:

const result = await FirebaseAuthentication.signInWithGoogle();

Other information:

Capacitor doctor:

💊   Capacitor Doctor  💊 

Latest Dependencies:

  @capacitor/cli: 4.1.0
  @capacitor/core: 4.1.0
  @capacitor/android: 4.1.0
  @capacitor/ios: 4.1.0

Installed Dependencies:

  @capacitor/cli: 4.1.0
  @capacitor/core: 4.1.0
  @capacitor/android: 4.1.0
  @capacitor/ios: 4.1.0

[success] iOS looking great! 👌

Is your feature request related to a problem? Please describe:

Auth state persistence specifies how a user session is persisted on a device. You can specify how the Authentication state persists when using the Firebase JS SDK.

Describe the solution you'd like:

Add method setPersistence.

Describe alternatives you've considered:

Additional context:

https://firebase.google.com/docs/auth/web/auth-state-persistence

Pull request checklist

Please check if your PR fulfills the following requirements:

• [ ] The changes have been tested successfully.
• [ ] A changeset has been created (npm run changeset).

Close #26

Is your feature request related to a problem? Please describe: Upgrading an anonymous user requires you to link the anonymous account with a credential. This operation will fail if the credential is already associated with another account. A common use case at this point is to sign in to the existing account (so that a single Sign in with Apple button press can intelligently "register" [upgrade the anonymous account] or sign into an existing account with one click).

For a lot of other auth providers the original credential can be reused for the sign in operation. But for Apple, the original credential can't be reused. However, Firebase automatically provides an updated credential key within the error (FIRAuthErrorUserInfoUpdatedCredentialKey) that can be used afterwards for the sign in operation.

Without this updated credential key it's not possible to implement a sign in/register flow using native Apple Sign In for apps that use anonymous accounts.

Describe the solution you'd like: If FirebaseAuthentication.linkWithApple fails and the firebase error code is 'auth/credential-already-in-use', then there should be an updatedCredentialKey property that's added on to to the error that contains the retry token and a way to then sign in to Firebase using the updated credential.

Describe alternatives you've considered: From what I've seen, the only alternative would be to show the sign in screen twice to the user, but the UX on this would be confusing and not ideal.

Without the FIRAuthErrorUserInfoUpdatedCredentialKey there are no real/proper alternative solutions that'll work.

Additional context: This isn't a problem if your app doesn't use anonymous accounts since FirebaseAuthentication.signInWithApple will already either register or login for you.

We only need this for iOS in our app. I'm going to try and implement the iOS fix for this when I get time, but my Swift knowledge isn't great so I'm sure somebody else might be able to get it done faster if they wanted to.

Is your feature request related to a problem? Please describe:

firebase now supports custom OpenID and SAML providers

Describe the solution you'd like:

add a method like signInWithCustomProvider

Describe alternatives you've considered:

NA

Additional context:

Android implementation IOS implementation Web Implementation

Is your feature request related to a problem? Please describe: Remote Config allows for storing JSON values like arrays and objects but I don't think currently using the available methods those can be accessed.

Describe the solution you'd like: I would like to have some kind of support for retrieving JSON data from the Remote Config.

Describe alternatives you've considered: I tried getting the data using getString in hopes that I could just JSON.parse it but it doesn't appear that works. An argument could also be made for just flattening out objects but this doesn't work with arrays and sometimes it's nice to group a larger set of settings into a kind keyed config value.

Additional context: I'm not sure how to do this with the web SDK but for Android and iOS they provide an asByteArray method which can be used to get array and object data to return to the client. Here are some snippet that might be helpful that I've used in some of my own custom projects:

Android

@PluginMethod
    public void getArray(PluginCall call) {
        final String name = call.getString("name", "");

        if (!initialized) {
            call.reject("Remote Config has not been initialized!");

            return;
        }

        if (name == null || name.equals("")) {
            call.reject("Remote Config name is required!");

            return;
        }

        final byte[] value = getRemoteConfigValue(name).asByteArray();
        final JSObject result = new JSObject();

        try {
            final JSArray array = new JSArray(new String(value));

            result.put("name", name);
            result.put("type", "array");
            result.put("value", array);

            call.resolve(result);
        } catch (JSONException e) {
            call.reject("Unable to parse Remote Config array: " + e.getLocalizedMessage());
        }
    }

@PluginMethod
    public void getObject(PluginCall call) {
        final String name = call.getString("name", "");

        if (!initialized) {
            call.reject("Remote Config has not been initialized!");

            return;
        }

        if (name == null || name.equals("")) {
            call.reject("Remote Config name is required!");

            return;
        }

        final byte[] value = getRemoteConfigValue(name).asByteArray();
        final JSObject result = new JSObject();

        try {
            final JSObject json = new JSObject(new String(value));

            result.put("name", name);
            result.put("type", "object");
            result.put("value", json);

            call.resolve(result);
        } catch (JSONException e) {
            call.reject("Unable to parse Remote Config object: " + e.getLocalizedMessage());
        }
    }

iOS

@objc func getArray(_ call: CAPPluginCall) {
        let name = call.getString("name") ?? ""
        
        if !initialized {
            call.reject("Remote Config has not been initialized!")
            return
        }
        
        if name.isEmpty {
            call.reject("Remote Config name is required!")
            return
        }
        
        let value = self.remoteConfig?.configValue(forKey: name)
        
        do {
            let json = try JSONSerialization.jsonObject(with: value!.dataValue, options: []) as? [Any]
            
            call.resolve([
                "name": name,
                "type": "array",
                "value": json ?? []
            ])
        } catch {
            call.reject("Unable to parse Remote Config object!")
        }
    }

@objc func getObject(_ call: CAPPluginCall) {
        let name = call.getString("name") ?? ""
        
        if !initialized {
            call.reject("Remote Config has not been initialized!")
            return
        }
        
        if name.isEmpty {
            call.reject("Remote Config name is required!")
            return
        }
        
        let value = self.remoteConfig?.configValue(forKey: name)
        
        do {
            let json = try JSONSerialization.jsonObject(with: value!.dataValue, options: []) as? [String : Any]
            
            call.resolve([
                "name": name,
                "type": "object",
                "value": json ?? {}
            ])
        } catch {
            call.reject("Unable to parse Remote Config object!")
        }
    }

Is your feature request related to a problem? Please describe:

Default values are currently not officially supported and have to be implemented with a workaournd.

Describe the solution you'd like:

It would be great if you don't need this workaround and can tell Firebase Remote Config the default values. Add a FirebaseRemoteConfig.setDefaults(...) method.

Describe alternatives you've considered:

Additional context: