remoteFetchAsync not working

[wheels_2go]

Today any script that I was using remoteFetchAsync (to avoid CORS errors) is giving me this error:

 j: Error: Bad request: <root>.requestJson is missing

This error comes up on a few requests to different unrelated APIs. Additionally, some which work using regular fetch give this error when using remoteFetchAsync.

These scripts were working fine until now. Any ideas?

[eejeremy]

Yes this is happening to me today to, on a script that had been working fine for a very long time.  Not sure what to do, this is affecting our work flow, hoping it's resolved soon!

[spaceman]

Also having the same business critical issue here. Please roll back your latest deployment/PR. Your int. test failed at capturing this bug.

[ivalles]

Also having this critical issue. It's stopping our workflow.

[quyvo]

I also have this issue, I tried to use remoteFetchAsync with method POST or PUT, but this method actually called the GET method, which is totally wrong.

[siriwat]

// line 71 here
let response = await remoteFetchAsync(webhookUrl, {
    method: 'POST',
    body: JSON.stringify(dataJSON),
    headers: {
        'Content-Type': 'application/json',
    },
});

Me also, the code worked before until now.

On my side, I found only the account with the Owner permission still works, but the error occurs on the other account permission types e.g. Creator/Editor/...

*** Update 1 *** It now shown this error regardless of account permission, just after I re-login the owner account now face the same issue as everyone. ***

*** Update 2 *** SOLUTION !! - Migrate extension script to automation script, then we could run away from this problem *** See how 👉 Re: remoteFetchAsync not working - Page 2 - Airtable Community

[quyvo]

I have an owner account, but the error still occurs on my side saddly.

[siriwat]

Ahh, it worked on the Owner account until I do logout. Then login back give me error same as everyone now.

*** Update *** Runaway solution here 👉 Re: remoteFetchAsync not working - Page 2 - Airtable Community

[aproli90]

Any updates on this issue so far? Business critical issue for us. 

[quyvo]

I tried to use a bypass CORS extension (e.g https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf) (or enable CORS on API server), then update the script to use fetch instead of remoteFetchAsync. This is a workaround solution while waiting for AirTable to fix this.