ExpoKit: Pod install fails

Dear community,

I am trying to complete a run of pod install for an app that was built based on Expo SDK 36 and using the ExpoKit workflow.

I know that ExpoKit was deprecated after SDK 36, and that the last ExpoKit version came with SDK 38. Further, I am aware that existing ExpoKit apps would no longer receive fixes or feature updates. According to “Migrating from ExpoKit”, apps in the App Store and Play Store are supposed to “continue to run indefinitely”. But would the pod installation break?

Running pod install provides me with the following error:

[!] Error installing ExpoKit
[!] Failed to download 'ExpoKit': [!] /usr/local/bin/git clone http://github.com/expo/expo.git /var/folders/cz/ybg587w155j2dh3wcqtnnl6r0000gn/T/d20210624-34970-186htmu --template= --single-branch --depth 1 --branch ios/2.14.1

Cloning into '/var/folders/cz/ybg587w155j2dh3wcqtnnl6r0000gn/T/d20210624-34970-186htmu'...
warning: redirecting to https://github.com/expo/expo.git/
warning: Could not find remote branch ios/2.14.1 to clone.
fatal: Remote branch ios/2.14.1 not found in upstream origin

Running pod --version returns 1.9.2.

There are some older posts (2019 and before) on the forum related to the issue I am experiencing (e.g. https://forums.expo.dev/t/pod-install-fail-to-download-expokit-2-9-0/), and I have tried the suggestions there (brew install git-lfs or pod repo update etc), but to no avail.

Looking at the git repository, there are no tags/branches that match the branch that pod install is trying to clone (ios/2.14.1).

Is there anything else I can do to get the ExpoKit pod/source? Of course, the project would need to migrate to Bare, but being able to install ExpoKit again in the meantime would be good regardless.

Thank you very much.

Update: Without any change to the Podfile or any other file in the project (and no change to the cocoapods version installed), the ExpoKit is now found again and installs successfully. I can now also find it manually in Release ios/2.14.1 · expo/expo · GitHub - there were no connectivity issues before and I did not find matching tags/releases/branches listed when I checked manually after pod install had failed, but they’re visible and pod installs fine now.

1 Like

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