client functions don't seem to be working

[mpelzsherman]

I'm getting empty arrays from both listenXHR and waitForXHR.

It looks like the clientListen function isn't getting called.

I tried uncommenting this console.warn:

    api.execute(_client.clientListen, [], function (res) {
        console.warn('Listening XHR requests');
    });

... and I see the message, but I added some more console.log messages in client.js and the clientListen function is not being called.

Is this project being actively maintained? We would love to use it but there seem to be some pretty major bugs in it. Thanks!

[procyon-chao]

Also interested

[mpelzsherman]

I should add that we've realized this lib won't work for us because we are using the JS fetch API which does not use XmlHttpRequest.

The basic approach of "monkey-patching" XmlHttpRequest does work fine for XHR requests though. I just wasn't able to get it working.

[Pieras2]

How? I also made changes in source by adding an additional listener but not all XHRs were caught and only worked for single specific method described in help wt., 19 maj 2020, 18:19 użytkownik Michael Pelz-Sherman < [email protected]> napisał:

…

I should add that we've realized this lib won't work for us because we are using the JS fetch API which does not use XmlHttpRequest. The basic approach of "monkey-patching" XmlHttpRequest does work fine for XHR requests though. I just wasn't able to get it working. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMUVMH4BV62WJRVSHFCECM3RSKWPJANCNFSM4NA2CCLQ> .

[procyon-chao]

I should add that we've realized this lib won't work for us because we are using the JS fetch API which does not use XmlHttpRequest.

The basic approach of "monkey-patching" XmlHttpRequest does work fine for XHR requests though. I just wasn't able to get it working.

Were you able to find a better library?

[mpelzsherman]

Were you able to find a better library?

No, we ended up using a different solution.

@Pieras2 sorry I'm not sure what you are asking. Sounds like neither of us was able to get this working.

[Pieras2]

I made it working but not for all HXRs I needed. I even wrote somewhere what to change to make it work. I write from cellphone, will try to find it tommorow and give link. Anyway I was using line listenXhr() and do some request and then there was a command to parse listened data. wt., 19 maj 2020, 21:06 użytkownik Michael Pelz-Sherman < [email protected]> napisał:

…

Were you able to find a better library? No, we ended up using a different solution. @Pieras2 <https://github.com/Pieras2> sorry I'm not sure what you are asking. Sounds like neither of us was able to get this working. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMUVMHZB23S6X3EHKAKNBNLRSLKCDANCNFSM4NA2CCLQ> .

[Pieras2]

Fortunately easily found. Please look at #45 (comment) wt., 19 maj 2020, 21:08 użytkownik Pieraś <[email protected]> napisał:

…

I made it working but not for all HXRs I needed. I even wrote somewhere what to change to make it work. I write from cellphone, will try to find it tommorow and give link. Anyway I was using line listenXhr() and do some request and then there was a command to parse listened data. wt., 19 maj 2020, 21:06 użytkownik Michael Pelz-Sherman < ***@***.***> napisał: > Were you able to find a better library? > > No, we ended up using a different solution. > > @Pieras2 <https://github.com/Pieras2> sorry I'm not sure what you are > asking. Sounds like neither of us was able to get this working. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#48 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AMUVMHZB23S6X3EHKAKNBNLRSLKCDANCNFSM4NA2CCLQ> > . >

[procyon-chao]

Fixed my issue. It was pretty silly- I didn't read the documentation close enough and thought these lines were the same. I changed to the es5 configuration and it all works fine now.

[Pieras2]

Fixed my issue. It was pretty silly- I didn't read the documentation close enough and thought these lines were the same. I changed to the es5 configuration and it all works fine now.

Lucky You :)