From 90ea02056dd05e4c41265e4c03a93284139cc2dc Mon Sep 17 00:00:00 2001
From: Clint Purser <clintpurser@gmail.com>
Date: Fri, 10 Jan 2025 14:00:31 -0500
Subject: [PATCH] remove idTokenHint assert

I am wondering if there is a specific reason for this assert?

Currently we want to only supply our postLogoutRedirectUrl but not the idTokenHint in our app. We tried using the additionalParameters field to supply only the postLogoutRedirectUrl, but that causes fatal exception in android.

Would be nice to remove this assert, unless there is a reason with OpenID why we'd want to enforce it like this.

Let me know!
Thank you!
---
 .../lib/src/end_session_request.dart                           | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/flutter_appauth_platform_interface/lib/src/end_session_request.dart b/flutter_appauth_platform_interface/lib/src/end_session_request.dart
index 60213fc5..0c1cff12 100644
--- a/flutter_appauth_platform_interface/lib/src/end_session_request.dart
+++ b/flutter_appauth_platform_interface/lib/src/end_session_request.dart
@@ -13,8 +13,7 @@ class EndSessionRequest with AcceptedAuthorizationServiceConfigurationDetails {
     String? issuer,
     String? discoveryUrl,
     AuthorizationServiceConfiguration? serviceConfiguration,
-  }) : assert((idTokenHint == null && postLogoutRedirectUrl == null) ||
-            (idTokenHint != null && postLogoutRedirectUrl != null)) {
+  }) {
     this.serviceConfiguration = serviceConfiguration;
     this.issuer = issuer;
     this.discoveryUrl = discoveryUrl;