Close Menu
  • Home
  • AI
  • Big Data
  • Cloud Computing
  • iOS Development
  • IoT
  • IT/ Cybersecurity
  • Tech
    • Nanotechnology
    • Green Technology
    • Apple
    • Software Development
    • Software Engineering

Subscribe to Updates

Get the latest technology news from Bigteetechhub about IT, Cybersecurity and Big Data.

    What's Hot

    Chinese Buses, European Fears, and the Truth About Connected Fleets

    November 11, 2025

    Google’s Plan to Fix a Broken System

    November 11, 2025

    swift – IOS app not opened or prompted to open when Universal Link used

    November 10, 2025
    Facebook X (Twitter) Instagram
    Facebook X (Twitter) Instagram
    Big Tee Tech Hub
    • Home
    • AI
    • Big Data
    • Cloud Computing
    • iOS Development
    • IoT
    • IT/ Cybersecurity
    • Tech
      • Nanotechnology
      • Green Technology
      • Apple
      • Software Development
      • Software Engineering
    Big Tee Tech Hub
    Home»iOS Development»android – Expo 54 How to read bundled assets directly without extraction to cache?
    iOS Development

    android – Expo 54 How to read bundled assets directly without extraction to cache?

    big tee tech hubBy big tee tech hubNovember 1, 2025012 Mins Read
    Share Facebook Twitter Pinterest Copy Link LinkedIn Tumblr Email Telegram WhatsApp
    Follow Us
    Google News Flipboard
    android – Expo 54 How to read bundled assets directly without extraction to cache?
    Share
    Facebook Twitter LinkedIn Pinterest Email Copy Link


    I’m building an app with React Native / Expo SDK 54.
    The app bundles ~42,000 compressed HTML files (.zst format, ~224 MB compressed) that need to be accessible without network access.


    The Problem

    My production iOS build is 325 MB, but on first launch it creates another 330 MB in “Documents and Data” – basically duplicating all the assets.

    First launch also takes 1+ minute, which is unacceptable.


    What I’ve Tried

    Originally used Asset.fromModule() with imports for each doc file.

    • This causes Expo to automatically extract all imported assets to cache on first launch.
    • Hence the duplication and slow startup.

    Tried accessing files via Paths.bundle with the new File API (SDK 54).

    • Files don’t exist there.
    • I think this is because I’m importing them, so they’re embedded in the JS bundle, not included as separate bundled assets.

    Tested multiple asset access methods in production.

    • Only asset.localUri works, but it points to the extracted cache location (the duplication I’m trying to avoid).
    • Same with DownloadAsync – works, but duplicates the file and is slower.

    What I Want

    Files should be bundled in the app at build time, then read directly from the bundle on-demand when a user opens a doc page.

    It shouldn’t need to copy anything – just open the bundled file and read its bytes.

    This feels like it should be simple – the files are in the bundle (325 MB proves it).
    I just want to read them without Expo copying them to cache first.

    It also works perfectly in development builds and on web – it’s just native production builds causing issues.


    Current Architecture

    • Thousands of .zst compressed HTML files
    • Manifests with import statements for each file (auto-generated)
    • Files referenced by hash in the manifest, loaded on-demand when a user navigates to a page
    • zst filetype is added as external asset to the metro config
    • Currently not doing anything in app.json for these assets

    Questions

    1. Should I use assetBundlePatterns instead of imports?
      Would that make them accessible via Paths.bundle?

    2. Is there a way to bundle files without imports so Expo doesn’t auto-extract them?

    3. Is the asset.localUri extraction unavoidable when using Asset.fromModule()?

    4. Should I be using a completely different approach for bundling this many files?
      Or not bundle them at all and access them another way?


    Environment:

    • Expo SDK 54
    • React Native 0.81.5
    • EAS Build (production iOS builds)
    • New architecture enabled



    Source link

    Android Assets bundled cache EXPO Extraction Read
    Follow on Google News Follow on Flipboard
    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email Copy Link
    tonirufai
    big tee tech hub
    • Website

    Related Posts

    swift – IOS app not opened or prompted to open when Universal Link used

    November 10, 2025

    android – MissingPluginException(No implementation found for method OneSignal#initialize on channel OneSignal

    November 9, 2025

    How to access and modify Swift class properties using Frida on iOS?

    November 8, 2025
    Add A Comment
    Leave A Reply Cancel Reply

    Editors Picks

    Chinese Buses, European Fears, and the Truth About Connected Fleets

    November 11, 2025

    Google’s Plan to Fix a Broken System

    November 11, 2025

    swift – IOS app not opened or prompted to open when Universal Link used

    November 10, 2025

    A new era and new features in Azure Ultra Disk

    November 10, 2025
    About Us
    About Us

    Welcome To big tee tech hub. Big tee tech hub is a Professional seo tools Platform. Here we will provide you only interesting content, which you will like very much. We’re dedicated to providing you the best of seo tools, with a focus on dependability and tools. We’re working to turn our passion for seo tools into a booming online website. We hope you enjoy our seo tools as much as we enjoy offering them to you.

    Don't Miss!

    Chinese Buses, European Fears, and the Truth About Connected Fleets

    November 11, 2025

    Google’s Plan to Fix a Broken System

    November 11, 2025

    Subscribe to Updates

    Get the latest technology news from Bigteetechhub about IT, Cybersecurity and Big Data.

      • About Us
      • Contact Us
      • Disclaimer
      • Privacy Policy
      • Terms and Conditions
      © 2025 bigteetechhub.All Right Reserved

      Type above and press Enter to search. Press Esc to cancel.