Expose internal errors from method channel to help debugging

Signed-off-by: Mateus Felipe C. C. Pinto <[email protected]>

update_available_android/lib/update_available_android.dart

@@ -18,10 +18,13 @@ final class UpdateAvailableAndroidPlugin extends UpdateAvailablePlatform {
       return switch (available) {
         true => const UpdateAvailable(),
         false => const NoUpdateAvailable(),
-        null => const UnknownAvailability(),
+        null => throw StateError("The implementation should return either 'true' or 'false'. This means that there's an issue with the implementation."),
       };
-    } on PlatformException {
-      return const UnknownAvailability();
+    } on PlatformException catch (error, stackTrace) {
+      return UnknownAvailability(
+        error: error,
+        stackTrace: stackTrace,
+      );
     }
   }
 }

update_available_platform_interface/lib/src/availability.dart

@@ -22,8 +22,22 @@ final class NoUpdateAvailable implements Availability {
   const NoUpdateAvailable();
 }
 
-/// Represents that it was not possible to determine if an update is available
-/// or not.
+/// Represents that it was not possible to determine if an update is available.
 final class UnknownAvailability implements Availability {
-  const UnknownAvailability();
+  const UnknownAvailability({
+    this.error,
+    this.stackTrace,
+  });
+
+  /// The error that made it impossible to determine the availability.
+  ///
+  /// It will only be non-null if a [PlatformException] is thrown form the
+  /// method channel.
+  final Object? error;
+
+  /// The stack trace associated with [error].
+  ///
+  /// It will only be non-null if a [PlatformException] is thrown form the
+  /// method channel.
+  final StackTrace? stackTrace;
 }