Let Expo handle iOS credentials, if building new version of app not previously made with Expo, with no distribution certificate or provisioning profile in Apple Developer Account?

If I want to

  • build an iOS app that is a new version of an app currently on App Store, but not originally built with Expo,

then to establish continuity between the old version and the new version, do I need to

  • use the previous distribution certificate and provisioning profile?

When I log into the Apple Developer account, and check Certificates, Identifiers, and Profiles,

  • No distribution certificates or provisioning profiles exist.

  • The last build of the app was done in 2015.

  • Checking the app in App Store Connect does not show any provisioning profiles or distribution certificates either.

On running expo build: ios, would you recommend letting Expo handle these credentials, or should I try to make my own and then upload them?

Here’s expo diagnostics in case it’s relevant:

  Expo CLI 3.5.0 environment info:
      OS: macOS 10.14.6
      Shell: 3.2.57 - /bin/bash
      Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
      Yarn: 1.21.1 - /usr/local/bin/yarn
      npm: 6.13.4 - ~/.nvm/versions/node/v10.15.3/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
      Android Studio: 3.4 AI-183.6156.11.34.5692245
      Xcode: 10.3/10G8 - /usr/bin/xcodebuild
      expo: ^34.0.0 => 34.0.4
      react: 16.8.3 => 16.8.3
      react-native: https://github.com/expo/react-native/archive/sdk-34.0.2.tar.gz => 0.59.8
      react-navigation: ^3.11.0 => 3.13.0
      expo-cli: 3.5.0

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