Apple

On Apr 19, 2016, at 4:23 PM, Laurent Daudelin wrote:

I kinda remember having some similar issues over a week ago. I was setting up the keychain sharing and app groups capabilities when I ran into some weird errors from Xcode. I didn't think much about it, I re-typed the group ID and keychain group ID, possibly turned them off and back on. I didn't think much about it and I don't remember all the steps I took but at some point, it started working again. Sorry I can't be more specific.

Not a problem, Laurent. I just wanted to make sure that if I tell my execs that other people are having these issues as well, it will help explain why 1. we scripted a product release dry run on Thursday and it took twice as long on Friday and 2. why when I made a release for our CEO on Friday, that 1 out of 3 of the UDIDs I entered were actually in the product I sent to him and I had to do it again on Monday.

This helps a lot.

Thank you.

Alex Zavatone.

-Laurent.
--
Laurent Daudelin email@hidden
AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/
Logiciels Nemesys Software

On Tue, Apr 19, 2016 at 4:06 PM, Alex Zavatone <email@hidden> wrote:
I had a odd few things related to certs and provisioning profiles and iOS device IDs (Dev portal stuff) happen over the past week and I thought it was just me being stupid, but I thought I'd ask if anyone else has seen oddness with their dev certs, provisioning profiles, device ids or the like over the past week.

Last Thursday, we went through a dry run to submit our app to the iOS App Store and it went fine using the Application Loader.

Then on Friday, we got the completed app, I archived it and attempted to export it from Xcode 7.3 for upload to the App Store just like I did on Thursday and suddenly Xcode tells me that I don't have a valid identifier for the app that just worked the day before with the same provisioning profile.

Now, I made all these distro profiles and certs 2 months ago, exported my private key and distributed the profiles and my key and cert to the two other people who need to send out ad hoc IPAs. I'm the only guy with privs to create these within our company aside from my boss, who is more than happy to never ever touch them.

Additionally, no one clicked the terrible "do you want me to fix your codesigning issues" button in Xcode.

So, on Friday, I went in to our dev portal and recreated the distro profile and made sure that we had proper certs (we did) but some of the settings in the profiles were different from how I had left them. No one else is going to change them.

Also, last Friday, I added new UDIDs to our Ad Hoc * distro profile which we have been using for the past 2 months so I could send off a custom IPA to stakeholders and Monday, I find out that it didn't work. Not all of the UDIDs went in to the provisioning profile AND Xcode decided to use another provisioning profile for our app.

Now, sure, the other team could have changed the code signing, but if they do, they can't distribute ad hoc IPAs, because the only ad hoc profile that will work for them is the one that we have been using for the past 2 months that I made and distributed.

They have been distributing builds every day, so I know they were using the one I set up for them.

Now, I certainly could have messed something up, but this morning, I was preparing the same IPA for a new device, and when I clicked to add the UDID and then make the ad hoc provisioning profile again, it was not using our wildcard application id. It was using an application id from the first app in the list that I had never ever assigned to this profile.

I'm not sure if I was still rubbing the sleep out of my eyes, if other people have been seeing similar weirdness or if the developer portal website was updating poorly.

Has anyone else seen strange issues with their profiles, certs and UDIDs in the past week?

Thanks.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden