fix(demo): propagate CancellationException through outer catches

The previous commit added `catch (e: CancellationException) { throw e }`
inside `postNotification`, but the re-thrown cancellation was caught
again one frame up by `sendNotification` / `sendCustomNotification`'s
outer `catch (e: Exception)`, silently undoing the fix. The same
anti-pattern lived in `OneSignalService.fetchUser` (wrapping
`withContext(Dispatchers.IO)` + `connection.responseCode`) and
`MainViewModel.fetchUserDataFromApi` (wrapping `repository.fetchUser`,
the inner `withContext(Dispatchers.Main)`, and `delay(100)`).

Add a `CancellationException` re-throw clause ahead of each generic
`Exception` catch so structured-concurrency cancellation propagates all
the way up to the cancelled scope instead of being swallowed as a
misleading I/O error.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: fadi-george

examples/demo/app/src/main/java/com/onesignal/example/data/network/OneSignalService.kt

@@ -76,6 +76,8 @@ object OneSignalService {
             }
 
             return@withContext postNotification(notificationJson, "notification")
+        } catch (e: CancellationException) {
+            throw e
         } catch (e: Exception) {
             Log.e(TAG, "Error sending notification", e)
             return@withContext false
@@ -110,6 +112,8 @@ object OneSignalService {
             }
 
             return@withContext postNotification(notificationJson, "custom notification")
+        } catch (e: CancellationException) {
+            throw e
         } catch (e: Exception) {
             Log.e(TAG, "Error sending custom notification", e)
             return@withContext false
@@ -256,6 +260,8 @@ object OneSignalService {
                 Log.e(TAG, "Failed to fetch user (HTTP $responseCode): $errorResponse")
                 return@withContext null
             }
+        } catch (e: CancellationException) {
+            throw e
         } catch (e: Exception) {
             Log.e(TAG, "Error fetching user", e)
             return@withContext null

examples/demo/app/src/main/java/com/onesignal/example/ui/main/MainScreen.kt

@@ -4,7 +4,6 @@ import android.content.Intent
 import android.net.Uri
 import androidx.compose.foundation.Image
 import androidx.compose.foundation.background
-import androidx.compose.foundation.layout.Box
 import androidx.compose.foundation.layout.Column
 import androidx.compose.foundation.layout.Row
 import androidx.compose.foundation.layout.Spacer

examples/demo/app/src/main/java/com/onesignal/example/ui/main/MainViewModel.kt

@@ -17,6 +17,7 @@ import com.onesignal.user.state.IUserStateObserver
 import com.onesignal.user.state.UserChangedState
 import com.onesignal.user.subscriptions.IPushSubscriptionObserver
 import com.onesignal.user.subscriptions.PushSubscriptionChangedState
+import kotlinx.coroutines.CancellationException
 import kotlinx.coroutines.Dispatchers
 import kotlinx.coroutines.channels.Channel
 import kotlinx.coroutines.flow.Flow
@@ -234,6 +235,8 @@ class MainViewModel(application: Application) : AndroidViewModel(application), I
                     }
                     _isLoading.value = false
                 }
+            } catch (e: CancellationException) {
+                throw e
             } catch (e: Exception) {
                 android.util.Log.e("MainViewModel", "Error fetching user data", e)
                 withContext(Dispatchers.Main) {