eas-cli: EAS build fails on iOS with ** ARCHIVE FAILED **

Summary

I’m trying to build my project with EAS and I end up with the issue. I’ve made many changes but could not go pass the ARCHIVE FAILED error. Any help would be appreciated.

my app.json

{
    "expo": {
        "name": "bilibo",
        "slug": "bilibo",
        "owner": "XXXXX",
        "description": "Bilibo was built exclusively for students helping them to organise academic life, share experiences, create groups, prepare for exams, upload, share and store study materials, manage tasks, and many more.",
        "version": "1.0.0",
        "privacy": "hidden",
        "orientation": "portrait",
        "icon": "./app/assets/icon.png",
        "entryPoint": "./app/App.tsx",
        "splash": {
            "image": "./app/assets/splash.png",
            "resizeMode": "contain",
            "backgroundColor": "#ffffff"
        },
        "updates": {
            "fallbackToCacheTimeout": 0
        },
        "assetBundlePatterns": ["**/*"],
        "primaryColor": "#6a51c6",
        "ios": {
            "supportsTablet": false,
            "usesIcloudStorage": true,
            "infoPlist": {
                "UIBackgroundModes": "remote-notification",
                "NSUserTrackingUsageDescription": "The app uses this information to deliver personalized ads.",
                "NSCameraUsageDescription":"The app uses camera to upload photos directly to the app.",
                "NSLocationWhenInUseUsageDescription":"The app uses location to automatically set Country and City fields at registration.",
                "NSPhotoLibraryUsageDescription":"The app uses photo library to upload photos directly to the app."
            },
            "jsEngine": "hermes",
            "bundleIdentifier": "XXXXX"
        },
        "android": {
            "softwareKeyboardLayoutMode": "pan",
            "adaptiveIcon": {
                "foregroundImage": "./app/assets/adaptive-icon.png",
                "backgroundColor": "#FFFFFF"
            },
            "jsEngine": "hermes",
            "useNextNotificationsApi": true
        },
        "plugins": ["expo-tracking-transparency", 
            [
            "expo-document-picker",
            {
              "appleTeamId": "XXXXX"
            }
          ]]
    }
}

Managed or bare?

Managed

Environment

  EAS CLI 0.41.1 environment info:
    System:
      OS: macOS 12.1
      Shell: 5.8 - /bin/zsh
    Binaries:
      Node: 14.17.0 - /usr/local/bin/node
      Yarn: 1.22.17 - /usr/local/bin/yarn
      npm: 7.17.0 - /usr/local/bin/npm
    Utilities:
      Git: 2.32.0 - /usr/bin/git
    npmPackages:
      expo: ^43.0.0 => 43.0.0 
      react: 17.0.1 => 17.0.1 
      react-dom: 17.0.1 => 17.0.1 
      react-native: 0.64.3 => 0.64.3 
    npmGlobalPackages:
      eas-cli: 0.41.1
      expo-cli: 5.0.1
    Project workflow: managed

Error output

Compiling expo-task-manager Pods/EXTaskManager » EXTaskManager.m

▸ ** ARCHIVE FAILED **

▸ The following build commands failed:

▸ PhaseScriptExecution [CP-User]\ Generate\ app.manifest\ for\ expo-updates /Users/expo/Library/Developer/Xcode/DerivedData/bilibo-crdkdifzvghelvevlkgcthtngadr/Build/Intermediates.noindex/ArchiveIntermediates/bilibo/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/EXUpdates.build/Script-49F93F43B9AB98D31CB55A39585BC5D3.sh (in target 'EXUpdates' from project 'Pods')

▸ (1 failure)

** ARCHIVE FAILED **
The following build commands failed:
 PhaseScriptExecution [CP-User]\ Generate\ app.manifest\ for\ expo-updates /Users/expo/Library/Developer/Xcode/DerivedData/bilibo-crdkdifzvghelvevlkgcthtngadr/Build/Intermediates.noindex/ArchiveIntermediates/bilibo/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/EXUpdates.build/Script-49F93F43B9AB98D31CB55A39585BC5D3.sh (in target 'EXUpdates' from project 'Pods')

(1 failure)
Exit status: 65

Reproducible demo or steps to reproduce from a blank project

It’s difficult to reproduce this issue i’ve been working on my project for past 4 months and start to run builds only recently, in particular, today.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 22 (9 by maintainers)

Most upvoted comments

Yes, the issue will be closed after upgrading @expo/config-plugins.

@irakli-g fix was deployed yesterday