Thanks for reporting. Somebody will reach out over DMs to help troubleshoot this.
Same here, been like this for the last couple releases. I've done some testing and this happens to any nsec, new or old, created by other clients, but not with a nsec created by the Primal client. Downgrading versions also didn't help.
Primal Android app reads the relays from the content field of the contacts nostr event. I have just checked and both your and @Piriya ⚡🟧's contacts list have empty "content" fields. Because of that the app doesn't know where to post the notes and shows the error. Can you check if you have published your relays list on other client?
I have. My nsec was a vanity nsec created manually. But of course I have my relay lists broadcasted and it works on all other clients. (I mainly use Amethys, Nostrudel, Snort, Iris, Nostrmo)
I have and most other clients list the relay list correctly but indeed on Primal web it shows an empty relay list. Though on https://nosta.me/npub1rqlwyvfshkj2778cc0lv46geppfhgxc73uqfcc0zpz3gy5d07uasj6c9tx you can see it displays the list properly. On https://metadata-contacts-relays.pages.dev/ as well.
Actually Primal web also shows the relays, it's probably an app issue then. https://m.primal.net/HQGd.png
Just an update on this. Indeed the relay list was empty on Primal, even though other apps have no issue fetching it. So upon updating it on the web client the app now works flawlessly. What confused me with the relay page was that the section in the middle was empty (cause there was no relays set) so my focus went to the relay list on the right, which I thought was the actual list, not a fallback list (which is what I assume it is since there was no relay set in the proper section). Plus Primal seems to have an issue populating the middle section automatically if the account/keys pair was created on another client. I confirmed this by creating new keys on both Primal and other clients, then testing them both on the Primal Android app. TLDR; network settings page was confusing, adding relays to the correct section solved the issue. https://image.nostr.build/ee93ac931c1d8a7663b2891ee8eb062def95319763888c84538ef10d80bea90f.jpg