Nock: No match for request

Question

My nock call looks like as below

app_url='myshop.app.com'
result = nock(app_url, {
            reqheaders: {
                 "content-type": "application/json",
                 'authorization': 'Basic Auth'
            }
          })
        .get('/admin/products.json?collection_id=10001&limit=250&fields=id')    
        .reply(200, {
                "products": [
                { "id": 101},
                {"id": 102},
            ]
        });

Resolve :

(node:1378) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Nock: No match for request { .

But now,

==========updated=============

I have updated my call which is not throwing an error but now it is not intercepting the request....It is still hitting shopify to fetch the data

Consider adding a solution otherwise this is a very confusing post. How did you update your call? — captDaylight, Nov 20 '18 at 16:15

Zveroslav Kravets · Answer 1 · 2019-02-28T15:09:43.323

5

Just add flag in scope { allowUnmocked: true }

nock('https://host.com', { allowUnmocked: true })
    .post(`/path`)
    .reply(200, {answer: "any"});

edited Feb 28 '19 at 15:09

answered Feb 28 '19 at 15:04

Zveroslav Kravets

51
1
4

1

This is not right, it should be the other way around. You should not allow unmocked URL. – LEMUEL ADANE Nov 17 '19 at 07:22
For this case, check if there are no unnecessary body params being passed incorrectly: Example: `.post(\`/path/${id}\`, unecessaryBody)` should actually just be `.post(\`/path/${id}\`)` or the opposite, it requires a body param and you are not passing – Roni Castro Oct 28 '22 at 20:09

Rohit Varghese Sebastian · Answer 2 · 2017-12-02T10:44:47.310

1

This happens when a nock matching the URL being hit is not found. The url being hit is

https://myshop.app.com/admin/products.json?collection_id=201&limit=10&fields=id

as seen in the error message. The URLs you are nocking do not correspond to it.

Something like this should work.

app_url = "https://myshop.app.com/"
result = nock(app_url, {
        reqheaders: {
            "content-type": "application/json",
        }
    })
    .get('/admin/products.json?collection_id=201&limit=10&fields=id').
    .reply(200, {
        "products": [{
            "id": 101
        }, {
            "id": 102
        }, ]
    });

More details about the exact way to nock can be found in the Nock Documentation.

edited Dec 02 '17 at 10:44

answered Dec 01 '17 at 07:14

Rohit Varghese Sebastian

19
3

@user269867 Thats bad. Just noticed the trailing ',' in the products array, not sure if that creates issues. – Rohit Varghese Sebastian Dec 02 '17 at 10:49
@user269867 Any luck with the , removal ? – Rohit Varghese Sebastian Dec 05 '17 at 12:52
No, I changed some config not "," – user269867 Dec 05 '17 at 23:08
@user269867 Can you elaborate the config change that you made for it to work ? – Rohit Varghese Sebastian Dec 11 '17 at 14:25
This is not working and also no information of what you changed to make it work!! – DoArNa Jul 24 '19 at 14:38

LEMUEL ADANE · Answer 3 · 2020-05-13T00:41:36.873

0

The nocked URL must be exactly the same as the URL that would be executed by Node in order to avoid the 'Nock: No match for request' error. So all you need to do is:

nock('https://host.com')
 .log(console.log) // log the mocked URL so that you will know if they're 
                   // the same or not.
 .post(`/path`)
 .reply(200, {answer: "any"});

edited May 13 '20 at 00:41

answered Nov 17 '19 at 07:21

LEMUEL ADANE

8,336
16
58
72

Nock: No match for request

3 Answers3