[app-attest-env] Log the actual error behind guest-session App Attest failures

Guest session handshake fails silently after the challenge step - no
console output, just a generic "could not load" message in the UI.
DCAppAttestService errors (generateKey/attestKey/generateAssertion)
propagate up uncaught by anything that logs them. Add explicit logging
at each step so the real thrown error is visible instead of debugging
blind.
This commit is contained in:
Daniel Arantes Loverde
2026-07-31 14:05:29 -03:00
parent 0cf3ab7b4f
commit e9e3e9da1f
2 changed files with 24 additions and 3 deletions

View File

@@ -161,6 +161,7 @@ struct PublicLocationPickerView: View {
errorMessage = "Nenhum estado disponível no momento."
}
} catch {
print("[PublicLocationPickerView] loadLocations failed: \(error)")
errorMessage = "Não foi possível carregar. Tente novamente."
}
isLoading = false