Support for Expo iOS archive format

[riglar]

https://discord.com/channels/1206536148650950736/1304492009284698162/1304502357161410650

Let Expo users pass a .tar.gz or signed Expo URL to dcd.

This remove the need to download and wrap the iOS binary into a .zip

[riglar]

Additional expo request which could be included in this feature: https://discord.com/channels/1206536148650950736/1347602249320497225/1348848425277587557

[dannyBies]

Hi @riglar , any chance of this being added in the near future? It's the only thing preventing my company from fully committing to devicecloud

[riglar]

Hey @dannyBies

I'll see if we can get this scheduled in. Please can you share some specifics about your workflow? Either here or email support@devicecloud.dev for privacy.

When we do this, I want to make sure we adequately solve your use case.

[dannyBies]

Thanks, I can share the relevant part from my workflow. We're running a bunch of custom scripts on Azure Devops. We'd like to simplify some of these scripts and make it more performant as we currently have to download, extract and zip the app binaries that we retrieve from Expo.

      - bash: |
          # Check if the tag exists, if true, retrieve the binary ID from the tag
          if [ "$(BINARY_TAG_EXISTS)" == "true" ]; then
            echo "Tag exists. Retrieving binary ID from tag..."
            binary_id=$(git tag -l "${{ variables.UPLOADED_BINARY_TAG_NAME }}" --format="%(contents)")
            echo "Retrieved Binary ID from tag: $binary_id"
          
          # If tag does not exist, download and upload the artifact to DCD Cloud
          else
            echo "Tag does not exist. Downloading and uploading artifact..."
            
            # Define the file name and download the artifact
            APP_FILE_NAME=$(basename "$(BUILT_ARTIFACT_URL)")
            echo "Downloading artifact from $(BUILT_ARTIFACT_URL) to $APP_FILE_NAME..."
            curl -L -o "$APP_FILE_NAME" "$(BUILT_ARTIFACT_URL)"

            # Handle iOS-specific extraction and zipping if necessary
            if [ "${{ parameters.platform }}" == "ios" ]; then
                EXTRACTED_DIR="${APP_FILE_NAME%.tar.gz}"
                ZIP_FILE="${EXTRACTED_DIR}.zip"
                
                mkdir -p "$EXTRACTED_DIR" && tar -xzvf "$APP_FILE_NAME" -C "$EXTRACTED_DIR"
                (cd "$EXTRACTED_DIR" && zip -r "../$ZIP_FILE" "Cazoo.app")
                APP_FILE_NAME="$ZIP_FILE"
            fi

            # Upload the artifact to DCD Cloud and extract the binary ID from the output
            uploadDetails=$(dcd cloud --apiKey "$(DEVICECLOUD_API_TOKEN)" --flows=${{ parameters.flows_directory }} -e APP_ID=${{ variables.APP_ID }} "$APP_FILE_NAME" --include-tags=${{ parameters.test_suite }})
            echo "$uploadDetails"
            binary_id=$(echo "$uploadDetails" | grep -oP 'Binary uploaded with id: \K[0-9a-f-]{36}')
            echo "Binary ID: $binary_id"

            # Create a new tag with the binary id so we can reuse it in the future
            git config user.name "Azure Pipelines"
            git config user.email "<>"

            # Delete the existing tag locally and remotely (if they exist)
            git tag -d "${{ variables.UPLOADED_BINARY_TAG_NAME }}" || echo "Local tag ${{ variables.UPLOADED_BINARY_TAG_NAME }} does not exist"
            git push origin --delete "${{ variables.UPLOADED_BINARY_TAG_NAME }}" || echo "Remote tag ${{ variables.UPLOADED_BINARY_TAG_NAME }} does not exist"

            git tag -a "${{ variables.UPLOADED_BINARY_TAG_NAME }}" -m "$binary_id" "$COMMIT_HASH"
            git push origin "${{ variables.UPLOADED_BINARY_TAG_NAME}}"
          fi

          # Set the binary_id as an output variable for downstream jobs
          echo "##vso[task.setvariable variable=BINARY_ID;isOutput=true]$binary_id"
        displayName: Retrieve or Upload Binary ID
        name: setBinaryId

[riglar]

Thanks @dannyBies

We've got a fairly busy roadmap right now but I'll flagged it with the team and we'll try to squeeze it in as soon as possible.

[finalerock44]

This is now available in CLI 4.4.0!