Developers accidentally call Purchases.Configure() multiple times during scene reloads or singleton recreation in Unity applications.

Currently, repeated initialization may happen silently, which can make debugging more difficult and potentially lead to unexpected behavior.

Possible Improvement

• Detect repeated initialization calls
• Log a warning instead of silently reconfiguring

Example:

if (_configured)
{
    Debug.LogWarning("Purchases.Configure() has already been called.");
    return;
}

This could improve the developer experience and make initialization issues easier to identify.

Happy to help with a PR if this approach is acceptable.