Automatically manage signing not working

Question

Created Apr ’20

Replies 3

Boosts 1

Views 8.6k

Participants 4

So I'm at a loss here. I have a paid apple developer subscription but I can't for the life of me figure out how to publish my app to appstore connect.

Whenever I archive my app, go to Organizer and click "Distribute Content" the only options presented are "Built Products" and "Archive". I'm missing any option to push my app to appstore connect.

Obviously something is wrong with signing the app I figure.

I have "Automatically manage signing" turned on in xcode. Next I selected my Team (which is just me) and filled the bundle identifier. Now the Provisioning Profile says "None Required" and the signing certificate is "Development". That's ok for local builds, but I think this is stopping me from publishing it to the app store.

So far I registered my app id and created a provisioning profile for app distribution. I installed the profile which I could only manually set in xcode, but no joy.

Everything I read so far seems to suggest "automatically manage signing" should take care of all the certificates. The fact that its only creating a development certifacte seems to indicate something is wrong to me. I've been at this the entire day but I'm out of ideas right about now.

I'd be happy to hear if anyone recognizes this. For clarity, I'm trying to publish a MacOS app.

Boost

Answer 1

KMT OP

Apr ’20

What version Xcode on which macOS?

Is the app ID tied to your account used by any other dev/team account for any purpose? How many teams are you on?

What certs do you find in Keychain related to making/distributing apps?

> I installed the profile which I could only manually set in xcode

What was that process and why use it vs. simply double-clicking? Did you mean certificate vs. profile?

0

Answer 2

joerick OP

Nov ’20

Just had this issue. Xcode was giving me the option to "Distribute Content", instead of "Distribute App". The problem was that the archive created by Xcode contained another library that was being 'installed' during the build process. Take a look at the archive from Xcode and you'll see.

I suppose Xcode expects the build to just output one App. In my case, the fix was to go into the build targets that produced those files (e.g. libraries) and set the Skip install setting to YES. Then Archive comes up and offers to "Distribute App".

2

Answer 3

dferrero OP

Nov ’24

Just like @blaap, I too wasted most of a full day on this. My app uses a framework I built. The framework uses 'default build settings' including the "Skip install" set to NO.

I wanted to use the automatic signing but that always produced an archive with the "Distribute Content" that @joerick mentions. It had been a while since I setup an app in the store so I forgot that it should say "Distribute App".

Once I followed @joerick advice, I quickly found and changed Skip install to YES and BINGO, I have Distribute App and Validate App both enabled!!

Apple would do well to have some tips and suggestions so others don't burn up a day on this crap since the framework used default settings.

FWIW, I also unchecked "Allow Archiving for Simulator" because that seems to disable the Distribute App and Validate App options. Instead, I just created an archive for Any iOS

0