PayloadTooLargeError for Expo in React Native

Question

What is causing the PayloadTooLargeError error? I get it sometimes and also when the payload is a few KB (as far as I can figure out).

PayloadTooLargeError: request entity too large
    at readStream (/usr/local/lib/node_modules/expo-cli/node_modules/@expo/dev-server/node_modules/raw-body/index.js:155:17)
    at getRawBody (/usr/local/lib/node_modules/expo-cli/node_modules/@expo/dev-server/node_modules/raw-body/index.js:108:12)
    at read (/usr/local/lib/node_modules/expo-cli/node_modules/@expo/dev-server/node_modules/body-parser/lib/read.js:77:3)
    at jsonParser (/usr/local/lib/node_modules/expo-cli/node_modules/@expo/dev-server/node_modules/body-parser/lib/types/json.js:135:5)
    at call (/usr/local/lib/node_modules/expo-cli/node_modules/connect/index.js:239:7)
    at next (/usr/local/lib/node_modules/expo-cli/node_modules/connect/index.js:183:5)
    at serveStatic (/usr/local/lib/node_modules/expo-cli/node_modules/serve-static/index.js:75:16)
    at call (/usr/local/lib/node_modules/expo-cli/node_modules/connect/index.js:239:7)
    at next (/usr/local/lib/node_modules/expo-cli/node_modules/connect/index.js:183:5)

I found some solutions that you can set the limit to a higher value, but that's not specifically for Expo.io

There is no console.log used in the app

What expo command did you run that resulted in this error being thrown? — Sreeram Nair, Mar 15 '22 at 11:11
@user1469734 please share the steps to generate the same error. — Chandan, Mar 22 '22 at 19:09
In my case, I rendered a flat list, with the console in the render-item function removing the console log resolved the error. And adding a console log after re-start will print all list items. — JASBIR SINGH, Jun 30 '23 at 06:37

score 0 · Answer 1 · answered Mar 22 '22 at 10:24

The error you are seeing could be caused by one of the packages you are using which uses body parser.

In body parser there is an option to limit to request body size:

limit
Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the bytes library for parsing. Defaults to '100kb'.

Taken from here.

You can see a related SO questions here and here.

I also saw this GitHub issue for Expo-Cli

score 0 · Answer 2 · answered Nov 20 '22 at 15:36

I had the same problem, after a lot of trials, I figure it out. The issue is related to the way you fetch the data, you are continuously fetching the data from database, which cause this error.

The solution is to fetch the data only once,

useEffect(() => {


  }, []);

Here is code example to

useEffect(() => {

const fetchUser = async () => {
  try {
    let user = await AsyncStorage.getItem('user_id');

    let parsed = JSON.parse(user);

    setUserId(parsed);

    //Service to get the data from the server to render
    fetch('http://myIpAddress/insaf/mobileConnection/ClientDashboard/PrivateReplyConsulationTab.php?ID=' + parsed)
    //Sending the currect offset with get request
    .then((response) => response.json())
    .then((responseJson) => {
      //Successful response from the API Call
      setOffset(offset + 1);
      const pri = Object.values(responseJson[0].reply_list);

      setPrivateReplies(pri);

      setLoading(false);

    })
    .catch((error) => {
      console.error(error);
    });
  }
  catch (error) {
    alert(error + "Unkbown user name")
  }
    }
    fetchUser();
  }, []);

score -4 · Answer 3 · answered Mar 15 '22 at 11:18

-4

I think the storage is merging the old requests, so can you reset the async storage

AsyncStorage.clear()

answered Mar 15 '22 at 11:18

Sreeram Nair

2,369
12
27

1

Clear AsyncStorage? Why? – user1469734 Mar 15 '22 at 15:37
2

This is a great way to destroy a lot of your or other SDK settings – B-Tron of the Autobots Sep 12 '22 at 04:01

PayloadTooLargeError for Expo in React Native

3 Answers3