Can you please elaborate?

ThirdPartyEmailPassword.Google({ clientId: 'CLIENT_ID', clientSecret: 'CLIENT_SECRET', scope: ['profile', 'email'], }), We set on Node.js side this in the init. But it works only for web. For iOS and Android on Cloud Platforms we don't have any clientSecret and different CLIENT_IDS

We need to authenticate the code from the library on Node.js

On the same project on Google Cloud for iOS we and Android we have a different clientID and no secrets for iOS, but clientSecret is mandatory in Supertokens Node

Checkout our react native example: https://github.com/supertokens/supertokens-react-native/tree/master/examples/with-thirdpartyemailpassword

It does exactly what you are looking for

We don’t have a capacitor example yet unfortunately. So this example is the closest to your needs

Essentially, you can configure multiple google providers on the backend and can make them use different client ids

If you see the server/index.js file, we do a google.init with an empty clientID and secret.

Then if you see the frontend side: https://github.com/supertokens/supertokens-react-native/blob/master/examples/with-thirdpartyemailpassword/google.js

You call the signInUp API without the code, but instead you pass it the actual JSON object which you get from google