added logic to recreate AuthorizationService objects if disposed but …

…were needed
MaikuB · Oct 13, 2024 · 1491b2b · 1491b2b
1 parent 96c801f
commit 1491b2b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/flutter_appauth/CHANGELOG.md b/flutter_appauth/CHANGELOG.md
@@ -1,6 +1,7 @@
 ## [8.0.0-dev.4]
 
 * [Android] no functional changes but some code around dealing with `allowInsecureConnections` has been done in response to issue [554](https://github.com/MaikuB/flutter_appauth/issues/554)
+* [Android] added logic to help with issues like [205](https://github.com/MaikuB/flutter_appauth/issues/205) where an app tries to refresh a token but the instances of `AuthorizationService` have been disposed
 
 ## [8.0.0-dev.3]
 

diff --git a/...auth/android/src/main/java/io/crossingthestreams/flutterappauth/FlutterAppauthPlugin.java b/...auth/android/src/main/java/io/crossingthestreams/flutterappauth/FlutterAppauthPlugin.java
@@ -579,6 +579,10 @@ private void performEndSessionRequest(
   }
 
   private AuthorizationService getAuthorizationService() {
+    if (insecureAuthorizationService == null || defaultAuthorizationService == null) {
+      // There have been some reported instances where the services have been disposed but they're still needed e.g. to refresh token
+      createAuthorizationServices();
+    }
     AuthorizationService authorizationService =
         allowInsecureConnections ? insecureAuthorizationService : defaultAuthorizationService;
     return authorizationService;