Bug? Silent authorization flow failure when default browser is restricted

Bug Report: Garmin Connect iOS: Silent failure when default browser is restricted

App: Garmin Connect (iOS)
Area: OAuth authorization flow (3rd party app linking)
App version: 5.21.2 on iOS 26.2.1

Summary:
When completing a 3rd party OAuth flow, the Garmin Connect app attempts to redirect to the default browser. If the browser is disabled by iOS Screen Time restrictions, nothing happens: No error, no warning. The user is just returned to the Connect home screen with no indication of what went wrong.

Steps to reproduce:
1. On iOS, restrict Safari (or the default browser) via Screen Time settings
2. Open a 3rd party app that uses Garmin Connect OAuth
3. Complete the authorization flow in the Garmin Connect app
4. Observe: the redirect silently fails and the user is directed to the app's home screen.

Expected behavior:
The app should detect the failed redirect and display an error message, e.g. "Unable to open your default browser. Please check your Screen Time settings."

Likely cause:
The app appears to call `UIApplication.shared.open(_:)` without checking the completion handler result, or calls `canOpenURL(_:)` without handling the `false` case. In either scenario, iOS silently refuses to open the restricted browser and the app doesn't surface this to the user.