Proper way to prevent ACPCore.start() more than once

[booker-dragon]

Expected Behaviour

The app should not do ACPCore.start() again after reload by getting a status value from native code

Actual Behaviour

No API to get the status of SDK, whether it is properly started or not

Reproduce Scenario (including but not limited to)

Have SDK initialization on app start and some callback method after we await for the result from ACPCore.start()

Steps to Reproduce

Load the app and SDK should start properly, do a reload (CMD + R / R + R)

Platform and Version

React Native

Sample Code that illustrates the problem

async componentDidMount() {
    await ACPCore.start()
    // below line will never execute after a reload as ACPCore.start() never resolve when it is called more than once
    doSomethingHere()
}

Logs taken while reproducing problem

[nporter-adbe]

Hi,

This is expected behavior when you try to initialize the SDK more than once and should not occur in the real world. You should see a log with a message similar to: Can't execute Core start action more than once.. This is just the way the live reload works, It reloads all the Javascript and thus you lose all your state, however the state in your native code (iOS/Android) is saved so you get into a strange state.

Please follow the documentation suggestion of initializing the SDK via native code to avoid this issue among others.

https://github.com/adobe/react-native-acpcore#initializing-the-sdk

[nporter-adbe]

We're also going to work on a React Native fix so this promise is always resolved. I'll keep this issue updated with the progress.

[nporter-adbe]

@booker-dragon The fix has been released in v1.1.1, please upgrade.

[booker-dragon]

Appreciate!