`expo export` is not producing consistent assets

Description

Not sure if this is a problem for expo or travis ci instead but want to give it a shot here first.

It seems expo export is not producing consistent size of assets.
e.g our travis ci job runs expo export and the total size of exported folder is 134.5MB (754 objects). But when I do this from my mac, the total size of exported folder is more than 300MB (exact 754 objects again)

I’m pretty confused about this weird behavior and curious Is there anyway that could help debug this?

Expected Behavior

Two exports are of same/similar size around 300MB

Observed Behavior

Two exports are not of same size.

Environment

travis ci:

  Expo CLI 3.20.6 environment info:
    System:
      OS: macOS Mojave 10.14.6
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.16.3 - ~/.nvm/versions/node/v10.16.3/bin/node
      npm: 6.9.0 - ~/.nvm/versions/node/v10.16.3/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^37.0.0 => 37.0.3 
      react: 16.9.0 => 16.9.0 
      react-native: https://github.com/expo/react-native/archive/sdk-37.0.0.tar.gz => 0.61.4 
    npmGlobalPackages:
      expo-cli: 3.20.6

my own local mac:

  Expo CLI 3.20.1 environment info:
    System:
      OS: macOS 10.15.3
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.16.3 - ~/.nvm/versions/node/v10.16.3/bin/node
      npm: 6.9.0 - ~/.nvm/versions/node/v10.16.3/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.5 AI-191.8026.42.35.5977832
      Xcode: 11.3/11C29 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^37.0.0 => 37.0.3 
      react: 16.9.0 => 16.9.0 
      react-native: https://github.com/expo/react-native/archive/sdk-37.0.0.tar.gz => 0.61.4 
    npmGlobalPackages:
      expo-cli: 3.20.1

The export job link: https://travis-ci.com/github/clicktherapeutics/ct152-mobile/jobs/334340909. It’s private repo so not sure how much it helps

I’m sorry to hear about the problems, but I am not sure if we can help you much in terms of troubleshooting. I’d suggest starting a debug build, and compare the sizes of the objects included in the directory. Perhaps you have debug symbols turned on in your local build and has a lot of extra information and so on.

Hi @BanzaiMan:
Thanks for replying. I did try to export in debug mode. But upon running expo export ... the screen turned into the following which I believe has something to do with watchman?

So i can’t really proceed to see the final bundle size without resolving this first. Seems to me like a general issue with macos virtual machine with travis ci?

For anyone interested, I think a workaround right now is to expo export using linux virtual machine. The bundle size seems correct this time for me.

Imprint