This PR resolves a potential infinite loop of cancellations and retries in Data Connect that could occur in DataConnectCredentialsTokenManager if an auth or App Check token change notification was triggered synchronously during an active token fetch. Instead of immediately cancelling the active job when a token change is detected, the manager now awaits its completion and inspects the result to determine if the expected token has already been retrieved.

Highlights

• Awaits active jobs instead of cancelling: Refactored onTokenChanged() to await the in-flight getToken() job rather than cancelling it immediately. This prevents a cascade of cancellation-retry loops when token notifications are synchronous.
• Reuse of successful fetches: If the completed job returns the newly notified token, no further calls are made, reducing the total calls to the provider's getAccessToken() to exactly 1.
• Updated unit tests: Replaced the cancellation-behavior test with a synchronous-refresh test to verify that calling onTokenChanged during a fetch doesn't result in redundant provider calls.

• CHANGELOG.md
  • Added a entry for the infinite loop fix when Auth/App Check tokens are refreshed.
• DataConnectCredentialsTokenManager.kt
  • Removed the NewToken retry exception class.
  • Refactored onTokenChanged() to launch a coroutine that awaits the active job and evaluates the retrieved token against the new token, skipping the retry if they match.
• DataConnectAuthUnitTest.kt
  • Removed onTokenChanged() should cancel in-flight getToken() requests and retry.
  • Added onTokenChanged() called synchronously from getToken() to verify synchronous notifications don't trigger redundant calls.
  • Cleaned up unused imports.