auth Redirect Uri
The OAuth redirect URI this platform can actually receive, passed to the auth server's /start endpoint (which validates it against its exact-match allowlist).
Mobile platforms return the custom-scheme deep link from local.properties (BackendConfig.GOOGLE_REDIRECT_URI): the OS routes it back into the app. A desktop JVM process can't register a URL scheme with the OS, so its actual uses the RFC 8252 loopback pattern instead — a localhost HTTP listener started on first use, whose URL the system browser can always reach.
The OAuth redirect URI this platform can actually receive, passed to the auth server's /start endpoint (which validates it against its exact-match allowlist).
Mobile platforms return the custom-scheme deep link from local.properties (BackendConfig.GOOGLE_REDIRECT_URI): the OS routes it back into the app. A desktop JVM process can't register a URL scheme with the OS, so its actual uses the RFC 8252 loopback pattern instead — a localhost HTTP listener started on first use, whose URL the system browser can always reach.
The OAuth redirect URI this platform can actually receive, passed to the auth server's /start endpoint (which validates it against its exact-match allowlist).
Mobile platforms return the custom-scheme deep link from local.properties (BackendConfig.GOOGLE_REDIRECT_URI): the OS routes it back into the app. A desktop JVM process can't register a URL scheme with the OS, so its actual uses the RFC 8252 loopback pattern instead — a localhost HTTP listener started on first use, whose URL the system browser can always reach.
The OAuth redirect URI this platform can actually receive, passed to the auth server's /start endpoint (which validates it against its exact-match allowlist).
Mobile platforms return the custom-scheme deep link from local.properties (BackendConfig.GOOGLE_REDIRECT_URI): the OS routes it back into the app. A desktop JVM process can't register a URL scheme with the OS, so its actual uses the RFC 8252 loopback pattern instead — a localhost HTTP listener started on first use, whose URL the system browser can always reach.
RFC 8252 §7.3 loopback redirect for desktop: a JVM process can't register a custom URL scheme with the OS (the system browser would dead-end on skimbyte://… with "address is invalid"), so the browser is redirected to this localhost listener instead, which forwards the full callback URL — token query params included — into the shared GoogleAuthCallback bridge.
The OAuth redirect URI this platform can actually receive, passed to the auth server's /start endpoint (which validates it against its exact-match allowlist).
Mobile platforms return the custom-scheme deep link from local.properties (BackendConfig.GOOGLE_REDIRECT_URI): the OS routes it back into the app. A desktop JVM process can't register a URL scheme with the OS, so its actual uses the RFC 8252 loopback pattern instead — a localhost HTTP listener started on first use, whose URL the system browser can always reach.