eas-cli: Building iOS app invalidates provisioning profile when using document picker

Build/Submit details page URL

No response

Summary

I’ve migrated to EAS build and in the same time I’ve used iCloud service with expo DocumentPicker.

So I’m no sur which is causing this issue…

But each time I launch a new build I’m facing Provisioning profile (id: *******979) is no longer valid

If I answer Yes to Generate a new Provisionning Profile it generate a new one correctly and it works … But if I run the command again (like 10 sc later) the previous (freshly generated) provisionning profil is now invalid …

It may be linked to iCloud. I’ve added "usesicloudstorage": true in my app.json I also have this configured in my app identifier :

With an container named iCloud.<your_bundle_identifier> as mentionned in the documentPicker docs

$ eas --version
eas-cli/0.50.0 win32-x64 node-v16.13.1

Managed or bare?

Managed

Environment

npx expo-env-info

expo-env-info 1.0.2 environment info:
    System:
      OS: Windows 10 10.0.19041
    Binaries:
      Node: 16.13.1 - C:\Program Files\nodejs\node.EXE
      npm: 8.1.2 - C:\Program Files\nodejs\npm.CMD
    SDKs:
      Android SDK:
        API Levels: 30
        Build Tools: 30.0.3
        System Images: android-30 | Google APIs Intel x86 Atom
    IDEs:
      Android Studio: Version  4.2.0.0 AI-202.7660.26.42.7351085
    npmPackages:
      expo: ^43.0.0 => 43.0.5
      react: 17.0.1 => 17.0.1
      react-dom: 17.0.1 => 17.0.1
      react-native: 0.64.3 => 0.64.3
      react-native-web: 0.17.1 => 0.17.1
    Expo Workflow: managed

Error output

No response

Reproducible demo or steps to reproduce from a blank project

I think it happens with any blank project

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 10
Comments: 54 (6 by maintainers)

Most upvoted comments

Can we reopen this? This problem still happens to me with latest CLI versions.

rafatrace on Aug 10, 2022

very fresh and not stale

rickithadi on Oct 14, 2023

we’ll certainly investigate this at some point, however because this doesn’t actually cause any issues that we were aware of, it’s not a top priority. you can do one of the following options:

re-generate the profile as prompted to do, and there will be no negative side effects
set EXPO_NO_CAPABILITY_SYNC=1 to opt out of automatic capability syncing
run eas build -p ios --non-interactive to skip validating profiles until you need to re-generate one (eg: to add a new device uuid)

brentvatne on Oct 31, 2023

Same with OneSignal extension

imwexpex on Oct 31, 2023

Same problem as @pkreipke once adding OneSignal to the mix, now every build incorrectly says provisioning file is invalid and generates a new one, next build the exact same thing. We need a fix as it is very annoying and adding the env var is likely to cause issues for some when changing entitlements as https://github.com/expo/eas-cli/issues/1069#issuecomment-1277391690 mentions and not knowing/remembering this is the “fix”

ChromeQ on Jul 13, 2023

Issue is still here

mguyard on Mar 3, 2023

Yea we are facing this issue with my team too, it complicates all of our processes, solutions mentioned so far are avoiding the issue 😦

NicolasMarcinkowski on Mar 8, 2024

I had to delete my provisional profiles and certificates and create a new one while creating the build. Only then did this issue get resolved, but for that build only, in the new build again I am having the same issue. Expo needs to address this right now.

kuldip-simform on Feb 15, 2024

I am getting this same issue. If anyone have solution for this please let me know.

kuldip-simform on Oct 26, 2023

same here.

ddehghan on Oct 6, 2023

Well as far as I know I DO have to login for each build I want to send to testflight 😕

And btw the certificat page will be a huge mess in a while …

seba9999 on Apr 22, 2022

This sth we are aware of, We don’t have any plans to fix it in the near future, as far as I understand the only problem here is that profile is regenerated every time which is not a problem (you do not need to login to apple for every build)

wkozyra95 on Apr 21, 2022