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
Calling fetch to read a streamed response seems to buffer the response messages up to around ~500 characters before actually returning the first chunk of the response.
Each dot is one message streamed chunk returned from the http endpoint. Clearly visible, the first few hundred characters are buffered together somewhere. This is unwanted behavior.
Expected behavior: each chunk is rendered immediately.
Enabled experimental React Native Directory checks. Unset the EXPO_DOCTOR_ENABLE_DIRECTORY_CHECK environment variable to disable this check.
✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check native tooling versions
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check if the project meets version requirements for submission to app stores
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check npm/ yarn versions
✔ Check for issues with Metro config
✔ Validate packages against React Native Directory package metadata
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
The text was updated successfully, but these errors were encountered:
Just verified that this is still happening with the latest expo version 52.0.9
matthiasbayer
changed the title
[SDK52] [expo/fetch] Received data not rendered immediately
[SDK52] [expo/fetch] Unwanted response data buffering
Nov 21, 2024
Minimal reproducible example
https://github.com/matthiasbayer/expo-fetch-buffer-bug
What platform(s) does this occur on?
iOS
Where did you reproduce the issue?
in a development build, in Expo Go
Summary
Calling
fetch
to read a streamed response seems to buffer the response messages up to around ~500 characters before actually returning the first chunk of the response.Each dot is one message streamed chunk returned from the http endpoint. Clearly visible, the first few hundred characters are buffered together somewhere. This is unwanted behavior.
Expected behavior: each chunk is rendered immediately.
Environment
Expo Doctor Diagnostics
The text was updated successfully, but these errors were encountered: