Building iOS app invalidates provisioning profile when using document picker

seba9999 commented 2 years ago

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

kuldip-simform commented 6 months ago

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.

Yes, it's rather confusing how it works with different combinations of actions as well. I wish the expo team would prioritise this. Right now, I'm using EXPO_NO_CAPABILITY_SYNC=1 for CI, and hoping that it all works consistently. That's not a solution though.

Sometimes that, too, is not working for me. For instance I had to try 3 times yesterday only on 4th attempt I got proper working build in TestFlight.

NicolasMarcinkowski commented 6 months ago

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

github-actions[bot] commented 5 months ago

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

ChromeQ commented 5 months ago

Not stale

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

ChromeQ commented 4 months ago

Not stale

github-actions[bot] commented 3 months ago

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

ChromeQ commented 3 months ago

Still not stale

chrysb commented 2 months ago

Just started realizing that this is happening — why is invalidating the provisioning profile with every build? Seems egregious

kuldip-simform commented 2 months ago

Yep @chrysb It should not happen and they are not responding in any manner that why this is happening or when they are planning any fix.

jwktje commented 2 months ago

I'm having this problem too!

PriimeTime commented 1 month ago

I started having this problem after enabling signin with apple in firebase console (not sure if even related).

brentvatne commented 1 month ago

hey folks, here's where we're at on this:

you can opt out of having EAS manage your capabilities (which is what is leading to this behavior) with EXPO_NO_CAPABILITY_SYNC=1 eas build (original comment docs).
we are aware of the issue but aren't sure what the right approach is to fix it, and invalidating the provisioning profile doesn't have any negative side effects as far as we are aware, so we are focusing on higher priority work and will come back to this in the future when we have bandwidth to deal with it. please correct me if i am wrong and this is actively causing issues for your project.
if you would like to investigate and suggest a solution, it'd be much appreciated!

github-actions[bot] commented 2 weeks ago

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

ChromeQ commented 2 weeks ago

Not stale

expo / eas-cli