How to initialize Amplify Auth inside an SDK without access to the Application class?

[Marwa-Dakdouk-FOO]

I’m building an SDK (a wrapper around AWS Liveness) that internally uses Amplify Auth.
According to the documentation, Amplify initialization should be done in the Application class:

Amplify.addPlugin(AWSCognitoAuthPlugin())
Amplify.configure(applicationContext)

However, since my SDK is meant to be integrated by other apps, I don’t have control over their Application class and I’d like to minimize the setup required by the client.

In my case, the SDK receives its configuration dynamically from the backend at runtime, so initialization cannot be done once at app startup. Because of this, I’m currently calling:

val amplifyConfJson = "{ ... }" // JSON config from BE

fun initAwsLiveness(context: Context) {
    try {
        Amplify.addPlugin(AWSCognitoAuthPlugin())
        Amplify.configure(AmplifyConfiguration.builder(JSONObject(amplifyConfJson)).build(), context)
    } catch (ex: Exception) {
        Log.e("AwsLivenessHelper", ex.message ?: "")
    }
}

This function may be called multiple times (e.g., on retries or new SDK sessions)

My questions are:

1. Is it safe to call Amplify.addPlugin() and Amplify.configure() multiple times (on retries or new sessions)? Or could this cause internal issues such as duplicate plugin registration or exceptions?
2. If not recommended, is it acceptable for an SDK to handle this internally, i.e., to call these methods from within the SDK but ensure they are executed only once (by tracking configuration state with a flag)
3. More generally, what is the recommended pattern for initializing Amplify when:

• The SDK cannot depend on the host app’s Application class, and
• Configuration values are fetched dynamically from a backend?

[tylerjroach]

1. No Amplify.configure can only be called once. You will need to track the configuration state and prevent additional calls to configure Amplify.
2. Yes

Configuration values are fetched dynamically from a backend?
This is ok

I'd recommend adopting some sort of singleton pattern or 1 time instantiation wrapper. Amplify can be called at any time. The reason we request that it is called within the application class is because the application class is launched only once. It also prevents the scenario of someone trying to call an Amplify method before Amplify has been configured.

If your sdk wraps around these concerns of 1. guaranteeing configure is only called once and 2. Not calling Amplify methods on plugins until after configure is called, then you will be ok.