Building iOS app invalidates provisioning profile when using document picker
See original GitHub issueBuild/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
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:16 (5 by maintainers)
Can we reopen this? This problem still happens to me with latest CLI versions.
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)