Purchases.isConfigured always returns true

[Ankooo12]

• I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• I have searched the Community
• I have read docs.revenuecat.com
• I have searched for existing Github issues

Environment

• Output of flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.4, on macOS 15.0 24A335 darwin-arm64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] Connected device (10 available)
[✓] Network resources

• Version of purchases-flutter
>=3.24.0
• Testing device version
  Android API 34
• How often the issue occurs- every one of your customers is impacted? Only in dev?
  • Only in dev
• Debug logs that reproduce the issue

PurchasesError(code=InvalidCredentialsError, underlyingErrorMessage=Invalid API Key., message='There was a credentials issue. Check the underlying error for more details.') 

• Steps to reproduce, with a description of expected vs. actual behavior
  Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

1. Added dummy Api Key dummy.
2. Run the app.
3. Check that the message is printed in the console.
4. Hot restart the app.
5. Still That error

Describe the bug

I have added a dummy API key in Purchases.configure(configuration) and encountered error logs. However, when I call Purchases.isConfigured, it returns true. Please help resolve this issue. Note that it works fine when the API key is empty.

Additional context

I've tried multiple times, but the issue persists.

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[aboedo]

@Ankooo12 the isConfigured method will return true whenever at least one call to configure has been made in the lifecycle of the app, regardless of whether the API key is correct.

In hindsight maybe we could improve the API to take that into account, but this is as of right now the behavior.

What use case are you trying to solve? Maybe we can help figure it out

[Ankooo12]

We sell app templates, and we need to verify whether our customers have configured them correctly. It was working fine before, but I believe there might be an issue with the updates.