app build works fine with expo build:ios but crashes with eas

Expo Application Services (EAS)
1

eas --version = eas-cli/0.47.0 darwin-x64 node-v16.14.0
expo --version = 5.2.0
node --version v.16.14.0

expo diagnostics:

  Expo CLI 5.2.0 environment info:
    System:
      OS: macOS 12.2.1
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
      Yarn: 1.22.17 - /usr/local/bin/yarn
      npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
      Watchman: 2022.02.07.00 - /usr/local/bin/watchman
    Managers:
      CocoaPods: 1.11.2 - /usr/local/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
      Android SDK:
        API Levels: 29, 30
        Build Tools: 29.0.2, 31.0.0
        System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 4.0 AI-193.6911.18.40.6626763
      Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
    npmPackages:
      babel-preset-expo: 9.0.1 => 9.0.1 
      expo: ^44.0.3 => 44.0.6 
      react: ^17.0.2 => 17.0.2 
      react-dom: 17.0.1 => 17.0.1 
      react-native: 0.64.3 => 0.64.3 
      react-native-web: 0.17.1 => 0.17.1 
      react-navigation: ^4.4.4 => 4.4.4 
    npmGlobalPackages:
      eas-cli: 0.47.0
      expo-cli: 5.2.0
    Expo Workflow: managed

expo doctor

🎉 Didn't find any issues with the project!

I am able to build just fine with either expo build:ios or eas build -p ios, however the app thats built with expo build works fine, the app build with eas crashes often.

Any ideas? I need to resolve this as soon as I can.

Thanks, guys,
Chris

*update: from what ive read online, async storage doesnt work well in apps built with eas build. Is this a known issue?

2

any thoughts, @wodin ?

3

This is not something I’ve heard of. Where did you see this?

Off hand it’s hard to tell what’s wrong without more information.

Can you look through the Production errors part of the debugging documentation?

2 Likes
4

I am using sentry, and sentry reports:
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

Not sure how to track that down, since it doesn’t error at all on the build that was built with expo build:ios. It only errors on the app built with eas.

5

Try running the app in production mode to see if you can reproduce the problem

6

@wodin: what do you mean production mode? I am building in eas, then using transporter to upload to app store for test flight

7

I mean like this:

See if you get the same error when you do that and it might give you more information about where the error is coming from.

1 Like
8

Thank you, after receiving those tips, I was able to use the sentry generated error, and looked it up on google, and determined that I was calling a library wrong. I was able to change:

import App from './app/app'

to

import { App } from './app/app'

Thank you @wodin, as of right now, I will close, marking your answer the solution. If I have any further issues, I will create a new ticket.

Why that is only broken when eas builds eludes me. Perhaps, eas is more picky than expo build. Would like to know if this is true.

9

I don’t know why that was. I would have expected this to crash with either build system.

10

me too.

11

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