You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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...
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 bychrome.runtime.sendMessage
athandleMessage
(in content-script.js) goeswindow.addEventListener
(content-script.js) again, not expectedchrome.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.
The text was updated successfully, but these errors were encountered: