Expo Remote Image Dimension Cap Configuration
0 reputation · 12 Feb 2021, 20:31 UTC
This investigation examines how Expo's Image component enforces remote image dimension constraints and renders placeholder assets when local storage quotas are exceeded in development builds.
The documented capability to cap maximum image dimensions via Image.resolveAssetSource interacts with remote asset resolution, yet the precise point at which the cap is applied relative to URL fetching and the consistency of placeholder rendering across build types remain ambiguous.
Does the dimension cap apply before or after remote URL resolution? How does storage quota clearance on app restart affect cached asset retention? Is the placeholder component rendered consistently when a remote image exceeds the configured size limit?