Summary of changes

This pull request introduces robust error handling and retry logic for SDK initialization, making it easier for apps to detect and recover from initialization failures (such as network issues during cold starts). The changes add a new reactive error state, automatic retries with exponential backoff, and a manual reinitialization API, allowing for more resilient and user-friendly app startup flows.

Initialization error handling and state:

• Added a new initializationError StateFlow to Clerk and ConfigurationManager, allowing apps to observe and respond to initialization failures in real time. [1] [2]

Automatic retry logic:

• Implemented automatic initialization retries in ConfigurationManager with exponential backoff (up to 3 attempts), storing the last error and retrying on failure. [1] [2] [3] [4]

Manual reinitialization API:

• Added a public Clerk.reinitialize() method (and corresponding internal logic) to allow manual retry of initialization after all automatic attempts have failed. [1] [2]

Configuration and state management improvements:

• Stored configuration options for use in retry attempts and ensured error state is cleared on new initialization attempts. [1] [2] [3]

Detekt baseline updates:

• Updated the Detekt baseline to suppress new warnings related to long methods and parameter lists introduced by the retry and error handling logic.

Summary by CodeRabbit

• New Features

  • Enhanced SDK initialization resilience with automatic retries (up to 3 attempts with exponential backoff)
  • Added error state tracking to monitor initialization failures
  • Added manual reinitialization capability for error recovery

• Chores

  • Updated code quality baseline analysis

_{✏️ Tip: You can customize this high-level summary in your review settings.}