Android app builds forever and fails - no logs provided

Expo Development Tools
1

I’m building my android app. Everything goes fine (JS bundles are built and assets uploaded) until it gets uploaded to expo server. Even though turtle status shows 0 builds waiting in queue, my app stays in In Progress state forever and never gets built (eventually failing). Moreover, there are no any logs to diagnose this particular issue.

Any advice?
(to @expo team: I can provide my build id if necessary)

This is my environment:

Expo CLI 2.18.2 environment info:
    System:
      OS: macOS 10.14.3
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 8.11.4 - ~/.nvm/versions/node/v8.11.4/bin/node
      Yarn: 1.13.0 - ~/.nvm/versions/node/v8.11.4/bin/yarn
      npm: 5.6.0 - ~/.nvm/versions/node/v8.11.4/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^31.0.2 => 31.0.6 
      react: 16.5.0 => 16.5.0 
      react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1 
      react-navigation: ^3.0.9 => 3.0.9 
    npmGlobalPackages:
      expo-cli: 2.18.2
2

Hey @korac,

Are you still encountering an issue building? Regardless, if you could provide an affected build ID(s) that would be great.

Cheers,
Adam

3

hey @adamjnav,

Still encountering this issue.

Some of my affected builds’ ids:

Thanks for your help!

Regards,
Kristijan

4

Thanks for providing those build IDs. I brought this up internally and will circle back when we know more!

1 Like
5

Thank you for your effort!

6

One of your assets seems to be broken and it crashes build before logs are uploaded to s3

Fix will be released soon and invalid asset will be displayed in logs. In your case it was this file https://d1wp6m56sqw74a.cloudfront.net/~assets/d41d8cd98f00b204e9800998ecf8427e

1 Like
7

Thanks for your feedback!

However, I don’t have this file type in my project.
From your link it seems like a video/mp4 file type (and I only have three images and few fonts files).

8

How did you set assetBundlePaterns in your app.json?
Can you run expo export and check files in dist directory?

9

Like this: "assetBundlePatterns": ["**/*"].
Just ran expo export and I can confirm corrupted file being present in dist/assets/ folder.

10

resolved by limiting assets to:

"assetBundlePatterns": [
  "assets/images/*"
],

thanks for the support :clap:

11

Glad you got things figured out!

12

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.