Purchases.sharedInstance is null right after calling Purchases.configure

Hey ​@adam-bílek-d5de9a 

Thanks for those details, they are quite helpful in trying to understand what can be happening.

As to your questions and what could possibly be happening:

• Purchases.configure() is synchronous on Android and is intended to immediately initialize Purchases.sharedInstance. However, what you're encountering can happen when sharedInstance is accessed before configure() has run, or if there's a race introduced by dependency injection or lifecycle timing.

Even if you're calling configure() "right before" in code, a few edge cases can cause this:

• race condition from DI: if a class accessing sharedInstance is constructed before or concurrently with configure(), you may see this intermittently.

• multiple Purchases initializations: accidental double calling configure or parallel instantiations can cause undefined state.

In order to validate the above, could you sanity check a few things please:

1. Call Purchases.configure() in Application.onCreate(). This ensures it’s the very first thing initialized, avoiding lifecycle or DI conflicts;

2. Avoid injecting Purchases.sharedInstance (for now!) via DI. Instead, access it after configure() has run or consider wrapping access in a helper that verifies it's been configured. As a temporary check on if this changes the behaviour;

3. Enable debug logging (via this guide). By setting Purchases.debugLogsEnabled = true early in app startup to get more insight into when configure() is called and whether multiple initializations occur;

4. Guard usage with Purchases.isConfigured. As of recent SDK versions, you can use Purchases.isConfigured to confirm whether sharedInstance is safe to access. This might help you isolate problem flows.

Let me know what you find, happy to dig deeper if the issue persists!

Best,

Gui