bitrise-steplib / steps-ios-auto-provision

MIT License
20 stars 33 forks source link

New GUI Apple portal - developer portal apple id not provided for this build #126

Closed rachid-debu closed 3 years ago

rachid-debu commented 4 years ago

Hello

I face an error while trying to auto provision.

developer portal apple id not provided for this build

I have setup everything (I think). Here are screens of what I've setup so far.

api-apple-3

api-apple-2

api-apple-1

Since the GUI has changed, maybe there's something else that has to be done. Need help please

pigeon-archive commented 4 years ago

Hi @rachid-debu,

Can you please share a build link so I can look at your workflows? Please ensure support access is enabled (by going to project settings).

bitce commented 4 years ago

Hi @rachid-debu! The issue here is that you are using version 1.x.x of the step. The new method of authentication is introduced in 2.x.x and only available from that version and the new ones going forward. Please update the version and let us know how it goes!

rachid-debu commented 4 years ago

hi, thanks for answer

@non-binary example of build that fails: https://app.bitrise.io/build/c5ca24dc79298507

@bitce I can't see a 2.x.x version of iOS Auto provision (screen 1). I can see that another provision step exists (screen 2), but version do not match either.

Capture d’écran 2020-06-08 à 13 59 49

Capture d’écran 2020-06-08 à 14 02 23

bitce commented 4 years ago

Sorry for the confusion, the step was indeed released as a new step. You need to use the iOS Auto Provision step with App Store Connect API. The original step still uses the old method.

rachid-debu commented 4 years ago

Thanks. OK i'm using the iOS Auto Provision step with App Store Connect API now.

Can it be ran if I'm building the APP with a Scripts step ? I mean, my build is successful, but the provision is not. Looks like he can't find some variables.

Failed to analyze project: failed to find the main target of the scheme (Doyouno): failed to find scheme (Doyouno) in project: scheme Doyouno not found in Doyouno

https://app.bitrise.io/build/1717dca025d9baad#?tab=log

(maybe this is getting offtopic though)

edit: i'm opening a issue on the proper repo https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect/issues/7

kndl22 commented 4 years ago

Hi, I have the same issue: developer portal apple id not provided for this build

I'm using the iOS Auto Provision with Apple ID step version 1.5.3.

I've connected apple developer portal account at the team tab.

pigeon-archive commented 4 years ago

Hi @kndl22,

Can you please send a link to a build?

kndl22 commented 4 years ago

Hi, @non-binary here's he link: https://app.bitrise.io/build/c364f53088f01def#?tab=log

pigeon-archive commented 4 years ago

Your team tab shows that no account is connected. Please correct this by signing in over on the settings page and enabling it again.

Screen Shot 2020-07-07 at 7 24 39 AM

kndl22 commented 4 years ago

It shows my name attached there:

Screen Shot 2020-07-07 at 14 28 01
bitce commented 4 years ago

Hi @kndl22,

As described above in the thread, there are two separate steps by now.

The issue is that you are using the deprecated step, but have connected your account through the new API key method. You either have to use the new App Store Connect API step, or connect your account with the deprecated method.

kndl22 commented 4 years ago

Hi @bitce, Thanks for being responsive. The only step regarding provisioning i see in the list is iOS Auto Provision with Apple ID. "iOS Auto Provision step with App Store Connect API" doesn't exist in the list.

bitce commented 4 years ago

I see, thanks. Can you send us a screenshot of you searching for the step but it not appearing?

kndl22 commented 4 years ago

Found it, Had to change from the "Flutter" sign at the top to "All" and that did the magic.

I'm attaching screenshot in case someone else getting here because of this:

Screen Shot 2020-07-08 at 14 40 08 Screen Shot 2020-07-08 at 14 34 17

Right now I'm facing other build error: Failed to register device: json: cannot unmarshal object into Go struct field DevicesResponse.data of type []appstoreconnect.Device

But this is irrelevant for this topic.

bitce commented 4 years ago

Thanks @kndl22! I've created a task to make the step appear as we'd expect to, and be sure to reach out to us about this latest error too, I believe it's an issue with the step we're looking at already.

jposes22 commented 4 years ago

Same issue here with native project please fix it we cant sign projects!

bitce commented 4 years ago

Hi @jposes22,

Are you referring to the original error reported in the thread? If so, the answer is above, there are two steps with two different authentication methods. Make sure yours match!

rachid-debu commented 4 years ago

Hi, didn't follow this thread for a while.

@bitce in fact, this very step steps-ios-auto-provision never worked for me either.

So i'm using the deprecated method steps-ios-auto-provision-appstoreconnect from https://github.com/bitrise-steplib/steps-ios-auto-provision-appstoreconnect

I need to try again with steps-ios-auto-provision but I don't have much time for this (since the older is working, we are using it, it's fine).

@bitce feel free to close this issue. I won't close it because I fixed the issue by using another repo, so..

bitce commented 4 years ago

I see! I believe we discussed this, I was curious about @jposes22 specifically. It is the other way around though, steps-ios-auto-provision-appstoreconnect is the new version and the legacy one is the steps-ios-auto-provision.

github-actions[bot] commented 3 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

github-actions[bot] commented 3 years ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.