question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[iOS] runtimeVersion from Expo.plist ignored

See original GitHub issue

Summary

I know that the issue is not specific to the eas-cli itself, but rather to the build service, however, I still thought it fits best here (please correct me otherwise). The official documentation states that for a runtime version in a bare project you have to set EXUpdatesRuntimeVersion in the Expo.plist (see here). I did this, and when building the project locally I can see that when inspecting the built ipa file that the contained Expo.plist contains the runtime version (obviously). However, when building the app with eas build this configuration is ignored. The resulting ipa file’s Expo.plist doesn’t contain the runtimeVersion.

To me, it feels like Runtime Versions are not supported yet with eas build?

Managed or bare?

Bare

Environment

EAS CLI 0.40.0 environment info:
    System:
      OS: macOS 12.0.1
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 14.17.6 - ~/.nvm/versions/node/v14.17.6/bin/node
      Yarn: 1.22.11 - ~/.nvm/versions/node/v14.17.6/bin/yarn
      npm: 6.14.15 - ~/.nvm/versions/node/v14.17.6/bin/npm
    Utilities:
      Git: 2.33.1 - /usr/local/bin/git
    npmPackages:
      expo: ^43.0.1 => 43.0.3 
      expo-dev-client: ~0.6.3 => 0.6.3 
      react: 17.0.2 => 17.0.2 
      react-dom: 17.0.2 => 17.0.2 
      react-native: ~0.65.2 => 0.65.2 
      react-native-web: 0.17.5 => 0.17.5 
    npmGlobalPackages:
      eas-cli: 0.40.0
      expo-cli: 4.12.12
    Project workflow: generic

Error output

There is no error output by the CLI itself

Reproducible demo or steps to reproduce from a blank project

  1. Create a bare expo project (dev client)
  2. Set a EXUpdatesRuntimeVersion key value in the Expo.plist
  3. Build the iOS app with eas
  4. See how your set runtime version has been ignored in the final build artifact

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
jkhalescommented, Dec 16, 2021

Happy you were able to resolve this @hannojg, but @dsokal is right that this is weird behavior, thanks for bringing it to our attention!

1reaction
hannojgcommented, Dec 16, 2021

Yes, when setting the runtime version env when calling eas build everything works as expected. Closing this for now, thx!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Runtime Versions - Expo Documentation
For an iOS build, add an entry to the Expo.plist with the key EXUpdatesRuntimeVersion . The value is a string that represents the...
Read more >
@expo/configure-splash-screen | Yarn - Package Manager
This package provides CLI command that helps you configure expo-splash-screen module. You can use it to configure your native iOS and Android project ......
Read more >
EAS UPDATE fails with "invalid mapping" while building ...
Ok, so I found the problem: the metro-source-map update from 0.71.1 to 0.73.0 seems to have broken the update run.
Read more >
expo-updates - UNPKG
19, Configuration for iOS should be done in Expo.plist. ... a server you're developing, you may want to tell expo-updates to ignore the...
Read more >
Comparing 1620963863...244eda3d12 - tooot - Gitea
runtimeVersion : project.hasProperty('runtimeVersion') ... <meta-data android:name="expo.modules.updates. ... ios/tooot/Supporting/Expo.plist.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found