React Native index file initializes prior to the completion of the Salesforce login flow

[Hemanth-M-K]

I’ve been working with React Native’s new architecture in combination with the Salesforce Mobile SDK and noticed an interesting behavior in the development branch,

The React Native index file initialises before the Salesforce login flow completes.

Since index.js is already initialised, it executes the following call:

oauth.getAuthCredentials(
  (data) => {
    console.log("getAuthCredentials data", data);
  },
  (error) => {
    console.log("getAuthCredentials error", error);
  }
);

At this point, because the login flow hasn’t finished yet, the call falls into the error block. If I proceed with login afterward, the index file is not triggered again, so React Native is unaware that the login completed successfully.

When investigating further, I noticed a difference between the development branch and the master branch of the SDK:

In the development branch, createReactActivityDelegate uses the default React Native delegate with Fabric enabled:

override fun createReactActivityDelegate() =
    DefaultReactActivityDelegate(this, mainComponentName, fabricEnabled)

In the master branch, createReactActivityDelegate uses SalesforceReactActivityDelegate, which prevents the index file from being re-triggered after login.

[wmathurin]

Have you seen: https://github.com/forcedotcom/SalesforceMobileSDK-Templates/tree/dev/ReactNativeDeferredTemplate

It is a React Native template application that demonstrates how to support "deferred login" meaning having an application that loads before login to Salesforce and that defers login until some later point. That makes sense for application that do not require to make API calls at startup to function.

[Hemanth-M-K]

@wmathurin , Yes, I have used 'deferred login' in one of the applications, but there’s currently an open bug where oauth.authenticate does not resolve on Android. forcedotcom/SalesforceMobileSDK-ReactNative#247