on iOS, at least for an existing user, I am able to navigate to the "edit profile" page. I still need to check if it's possible to get there for new users also.
nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q We're building a onboarding flow using Yakihonne and have reached a blocking problem I think. A totally new NOSTR user, as far as I can tell, is not able to modify their KIND 0 (zero) profile data. Please see image below. For both existing user and new users, clicking either (1) or (2) does not lead to any kind of ability to modify profile data, which is confusing. After much searching, I realized that, as long as there is EXISTING KIND 0 (zero) data on the network, I can click (3), and that will allow me to edit the metadata. However for a NEW nostr pubkey -- which has no existing metadata set, as far as I can tell it is currently impossible to add any of this metadata using Yakihonne. Clicking (4) does not seem to do anything.
Discussion
I think your metadata didnt load properly but it does not mean it does not exist we tested this multiplr timr and it seems okay. Can you jump to DM for better communication ?
I suggest you test a user flow from a NEW user using Alby browser extension to provide the window.nostr
As I responded to you earlier this is the normal behavior, I'm not sure why your profile is not loading properly all at once.
Here is what works for us.... A new user of the Alby browser extension must currently first go here:
https://metadata.nostr.com/# .. and enter AT LEAST ONE piece of metadata... after that is done, then Yakihonne will allow the user to get to Edit Profile
That sounds like a bug to me. You should be able to fully on board, from start to finish, in the client app. Just like you can do with Amethyst or Primal. The requirement that users go to the metadata.nostr.com site to input some profile metadata before the user can go to YakiHonne and complete the process is unacceptable as far as I'm concerned. The process you've come up with is a functional workaround, but this is something YakiHonne needs to address immediately.
it has been fixed already the problem was the frwsh alby extension accounts 🙏