Generating (or quering) provisioning profile returns wrong result in some cases about eas-cli

[EvanBacon]

On main (without this update #127), I'm getting the following:

• eas.json - default
• Fresh ios.bundleIdentifier, android.package, and slug (reran expo eject) (basically it's a new, project)
  • slug - ejbtest10
  • ids - com.bacon.test.ejbtest10
• Added the following to provisioningProfile.ts at this line console.log('listProvisioningProfilesAsync: ', profileType, profiles);
• eas build -p ios

First run

listProvisioningProfilesAsync:  IOS_APP_STORE []

Second run -- I sent you the original copy

listProvisioningProfilesAsync:  IOS_APP_STORE [
  Profile {
    context: { providerId: 118573547, teamId: 'QQ57RJ5UTD' },
    id: '8P872ZYQ95',
    attributes: {
      profileState: 'INVALID',
      configuration: 'N/A',
      uuid: 'XX-6484-40c8-b1c5-ff4645e11c96',
      platform: 'IOS',
      bundlePlatform: 'IOS',
      createdDate: null,
      profileType: 'IOS_APP_STORE',
      templateName: null,
      name: '*[expo] com.bacon.test.ejbtest10 AppStore 2020-12-08T20:58:33.712Z',
      profileTypeLabel: 'App Store',
      profileContent: 'BIGLONG=',
      platformName: 'iOS',
      responseId: 'XX-4474-476d-9e9c-d1de6c7bbb6b',
      expirationDate: '2021-12-08T20:48:23.000+0000'
    }
  }
]

• change bundleIdentifier to com.bacon.test.ejbtest11 (never used this bundle id before) and run expo eject
• eas build -p ios

First run

listProvisioningProfilesAsync:  IOS_APP_STORE []

[wkozyra95]

Based on this output I'm guessing that you are able to reproduce the problem

• newly created profile is invalid profileState: 'INVALID',
• can't see that but I'm guessing that if you decode value that was in place of BIGLONG= it might have wrong bundle identifier

On What account did you run those builds? I see only adhoc builds here https://expo.io/accounts/bacon/builds ? Did the second run fail?

I debugged it a bit more and found that in my case BundleId.findAsync return multiple results, but current implementation supports only one. I added filter there

diff --git a/packages/app-store/src/connect/models/BundleId.ts b/packages/app-store/src/connect/models/BundleId.ts
index 2c85b86..6ae4827 100644
--- a/packages/app-store/src/connect/models/BundleId.ts
+++ b/packages/app-store/src/connect/models/BundleId.ts
@@ -79,9 +79,13 @@ export class BundleId extends ConnectModel<BundleIdProps> {
       identifier: string;
     }
   ): Promise<BundleId | null> {
-    const [bundleId] = await BundleId.getAsync(context, {
+   const r = await BundleId.getAsync(context, {
       query: { filter: { identifier } },
     });
+   console.log(r.filter(bundleId => bundleId.attributes.identifier === identifier));
+   const [bundleId] = r.filter(bundleId => bundleId.attributes.identifier === identifier);
     return bundleId ?? null;
   }

after that new profile is still marked as invalid but it contains the correct bundle identifier and builds finish successfully

[wkozyra95]

If I'm wrong about the example you gave and that INVALID status is unrelated and you are unable to reproduce that issue, then please try using an example I gave in the original post. bundleIdentifier: org.reactjs.native.example.testapp.tu on turtle-dev apple account. I sent you info on how to access that account on slack

[dsokal]

It seems this is not an issue now.