Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getRelays does not work properly #7

Open
jg1uaa opened this issue May 4, 2023 · 1 comment
Open

getRelays does not work properly #7

jg1uaa opened this issue May 4, 2023 · 1 comment

Comments

@jg1uaa
Copy link
Contributor

jg1uaa commented May 4, 2023

Some NIP-07 client does not work properly and I found iris and nostter gets getPubKeys first but Snort and NostrFlu requires getRelays.

I added many console.logs to background.js and content-script.js, it showed the message for getRelays sent by chrome.runtime.sendMessage at handleMessage (in content-script.js) goes window.addEventListener (content-script.js) again, not expected chrome.runtime.onMessage.addListener (in background.js).

And it could avoid eternal loop due to message.data.params was not defined in 'pass on to background' message.

I am not JavaScript/TypeScript guru, I cannot show how to fix this problem. But I hope this information will solve the problem.

@jg1uaa
Copy link
Contributor Author

jg1uaa commented May 4, 2023

debug console for background.build.js shows it returns the result of getRelays.
even if getRelays itself works properly, question that why clients does not work getRelays -> getPubKeys order still remains...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant