[Bug] Profile settings show “parse failed: error decoding response body” on first launch

Describe the bug
When I opened Sprout for the first time, it appeared to auto-log me in using an existing Nostr identity already available on my Mac. After opening Settings → Profile, the app showed a red error banner that says: “parse failed: error decoding response body.” The profile fields did not appear to load correctly.

To Reproduce:

Install and open Sprout on macOS
Allow the app to launch with an already available/logged-in Nostr identity on the machine
Open Settings
Stay on or navigate to the Profile tab
See error: “parse failed: error decoding response body”

Expected behavior:
I expected Sprout to load my relay profile successfully, or at minimum handle any auto-login/profile-loading issue gracefully with a clearer error message and usable profile settings.

Supporting Material
Screenshot attached showing the error in Settings → Profile:

Red banner message: “parse failed: error decoding response body”
Identity shown as npub1t2vge...pk0e
The app appears to have auto-authenticated me, likely because I was already logged in to other Nostr clients on my Mac

Environment (please complete the following information):

OS: macOS
Version: Tahoe 26.4

Additional context
This was my first time trying the app. I was already logged in to other Nostr clients on my Mac, so Sprout may have automatically picked up an existing identity/session. I am not sure whether that is expected behavior, but it may be related to the error. The issue appeared immediately when I opened the app and viewed the Profile settings.

Reproduce the issue on macOS by opening Settings → Profile after Sprout auto-authenticates an existing Nostr identity. Start by tracing the Profile loading flow and the response decoding that produces the banner; done means the relay profile loads correctly or the app presents a clearer, usable failure state.

Written by the indexing model from the issue text.