So, you have inadvertantly made me aware of a different issue I was not aware of lmao. Thank you!

It does seem that per the NIP-05 spec that you can only have one username in the json object: https://gothub.projectsegfau.lt/nostr-protocol/nips/blob/master/05.md

"if after finding that `bob@bob.com` has the public key `abc...def`, the user clicks a button to follow that profile, the client must keep a primary reference to `abc...def`, not `bob@bob.com`. If, for any reason, the address `https://bob.com/.well-known/nostr.json?name=bob` starts returning the public key `1d2...e3f` at any time in the future, the client must not replace `abc...def` in his list of followed profiles for the user (but it should stop displaying "bob@bob.com" for that user, as that will have become an invalid `"nip05"` property)."

So, that does explain one part. I also think I found the original root cause, which was a non-hex entry for a user, which may have errored out the Swift json parser. I now see users loading correctly again.

Appreciate you both jumping in here 👏