spotify/android-auth

📦 Version 4.0.1

• Fix: Ensure auth progress is preserved across configuration changes, preventing cases where a headless activity remains open and blocks user input.

📋 Changes

• Breaking Change: Added new `AuthorizationResponse.Type.CANCELLED` to differentiate user-initiated cancellations from technical errors.
• User cancellations (browser closed, back button pressed) now return `Type.CANCELLED` with `RESULT_CANCELED`
• Technical errors (malformed responses, missing data) return `Type.EMPTY` with `RESULT_OK`
• OAuth errors (e.g., `access_denied`) continue to return `Type.ERROR` with `RESULT_OK`
• Client applications should update their authorization result handling to account for the new `CANCELLED` type and `RESULT_CANCELED` result code.

📋 Changes

• Add mandatory redirect path pattern.

📋 Changes

• Requesting token now uses PKCE when:
• There is an installed Spotify app that supports PKCE.
• When web fallback is used.
• Propagate tracking parameters when opening the native login flow
• Token requests may return a refresh token if PKCE was used.

📋 Changes

• Introduced `RedirectUriReceiverActivity` for web based auth flow
• Restructured web based flow, removed `LoginDialog` class
• Made `AuthorizationClient` final
• Bumped to Gradle 7.5, AGP 7.4.2
• Bumped targetSdkVersion to 33
• Bumped androidx.browser to 1.5.0 and test dependencies

📋 Changes

• Introduced a new flavour store to generate a library called auth-store that default to the play store instead of `CustomTabsIntent`
• Exposed method to check if the Spotify application is installed

📋 Changes

• Fixed StackOverflowError at com.spotify.sdk.android.auth.browser.LoginDialog.onServiceDisconnected
• Fixed NullPointerException when creating CustomTabsIntent in LoginDialog
• Set LoginActivity launch mode to singleTask to avoid launching CustomTabs in a separate task

📋 Changes

• Removed unused code related to WebView and updated documentation

📋 Changes

• Replaced WebView usage with [Custom Tabs](https://developer.chrome.com/docs/android/custom-tabs/) since Google and Facebook Login no longer support WebViews for authenticating users.
• Removed `AuthorizationClient#clearCookies` method from the API. Custom Tabs use the cookies from the browser.
• Bumped targetSdkVersion to 31

📋 Changes

• Updated targetSdkVersion (API 30), buildTools and Gradle plugin
• Removed unused jcenter repository
• Conform to package visibility restrictions when targeting Android 11 (API 30)

📋 Changes

• Stability fixes on webview based redirect
• LoginActivity launchmode changed

📋 Changes

• Remove custom-tabs handling due to issues

📋 Changes

• Fixes an issue that produced a redirect error when the redirect uri contains CAPS.