Posts

Post not yet marked as solved
7 Replies
After pressing developer support further on this, the reply was:"It [I assume they mean 'the AppId'] is used on another account associated with another app record and will never be available for use in any other account ever."I asked them to clarify whether their use of the term 'account' referred to a team account or an individual user account, but they ignored the question and insist on continuing to use vague terms without clarification.So the bottom line is that our AppId containing our team identifier has somehow beome associated with some other mysterious app (our team only has one app in AppStore Connect) and is no longer available to us. The only alternative is to select a new bundle id, which would negatively impact our users and therefore is unacceptable.So if you're wondering why some apps are never made available via the Mac AppStore, it's because there's something seriously broken in either Apple's AppStore database or developer support organization.
Post not yet marked as solved
7 Replies
Thanks. After quoting your response to Developer Program Support, they say:Hello,Thank you for reaching out.The identifier you referenced in your email is already used in another account. You will need to use a new identifier.Regards,GarrenApple Inc.
Post not yet marked as solved
7 Replies
Thanks, I didn't realize the provisioning profile wasn't necessary for developer distribution. When I inherited this app it had one configured so I just assumed it was required.So with the AppId controlled by a user outside my organization, it sounds like we can notarize the app and continue to distribute it ourselves, but we'll never be able to put it in the Mac App Store unless we change the bundle id. Correct?I still don't understand why an AppId that contains our team id is not accessible to our organization. You stated in your earlier response that "it's the property of the team", but in an email to me developer support stated (verbatim): "I received response from our internal teams in regards to your bundle id request. We confirmed the bundle id was used in a different account. We can't approve your request to remove the identifier so we will have to create a new identifier for your app."
Post not yet marked as solved
7 Replies
We have an existing app with the AppId that we distribute through our website, but it has not been published in the Mac App Store. I've been working toward that (i.e. sandboxing) and now also getting the app notarized. But I just discovered that I can't generate a new provisioning profile with the explicit bundle id, and I don't think a wildcard bundle id will be accepted for notarization.