I'm a bit confused after reading a post from 4 years ago regarding the Apple ID and Bundle ID. I was told by someone with a very high reputation score that the Apple ID and Bundle ID are the same. But according to the post I read they aren't.
*****The possible duplicate question is the question that confused me. My question has to do with whether or not the App ID and Bundle ID are the same, and if that means I have full access to my code. That doesn't seem clear to me in the question from 4 years ago. Things may have also been updated.
My question also has to do with only seeing info.developersname.appname and not com.???.???
I had a company that has since disappeared develop my Demeters Harvest app. I am now working on trying to learn the basics before going with a new developer and I am confused about how to gain access to the XCode so a new dev can update the app that has some glitches.
When I go into my portal I see three provisioning files for the app with the same App ID: info.OLDDEVELOPERNAME.demeter. One is with XC in front and then there's a Wild Card too.
Are none of these the bundle that lets me work on my app? I don't know if these mean I do have the bundle or not.
Thanks.
I think I see your confusion. The Bundle ID and the App ID have to match, but they are not in fact the same thing. The App ID is what is in iTunes Connect, the Bundle ID is what is found in your app (Xcode project). You can't change your App ID once your app is in the store, and since your Bundle ID has to match your App ID to release your app, they are sometimes referred to as the same.
If you create a new project, you can set your Bundle ID to the App ID in the iTunes Connect, and it will be accepted by iTunes Connect.
EDIT: Picture of where to find accepted Bundle ID in iTunes Connect.
Related
I've been developing a Swift app for a while now on my own individual developer account linked to my longstanding everyday AppleId - so the AppleId also has all my bought music, apps, appleTV and other content etc etc. As I have developed the app I have realised that it has considerable commercial potential, and so would rather release it under an organization (a private limited company) than under my own individual name.
The app itself is relatively straightforward, it is self-contained other than having a single non-consumable in app purchase. I have not yet uploaded the app to AppStoreConnect, although I have set up the app name and the in app purchase on AppStoreConnect for testing purposes. I would like to release in the quickest way possible now. Using XCode 14.
What is the quickest, most straightforward and trouble-free way to achieve my goal? Should I:
Release it under my own individual developer account and then ask apple to change my individual account to an organization account? Are there any complications with this given that this dev account is attached to my personal AppleId? How long does it usually take Apple to achieve the change? Does the App remain on sale throughout? Are there ever any problems or is there anything else I should be aware of?
OR
Set up a totally fresh AppleId and create a new developer account for the organization on this id? (I appreciate this will cost extra money but am willing to bear the cost). If I do this, how do I transfer the app from my individual account to the organization account? Do I have to go through the Apple 'transfer an app' process? Are there any pitfalls with this? When the transfer is complete, how do I alter my XCode set up to continue working on the app under the new account? Also, as I have not yet submitted the app to AppStore (although I have set up the name / IAP ) can I simply use XCode to point the app at the new account and upload it to that instead without invoking the Apple 'transfer an app' process - how would I alter my set up on XCode to achieve this?
I am currently in the process of setting up the company, and should have necessary info eg DUNS no etc fairly shortly.
While I'm familiar with development itself and I've already released one paid app on the AppStore under my own individual account attached to my everyday AppleId, this seemed to be a relatively simple and automated procedure. My main difficulties with my current problem seem to stem from the fact that I have never worked as part of a swift development team, and I understand very little around the actual 'architecture' of app development, eg XCode signing / teams / bundle ids etc, and I'm really struggling to understand the technicalities of the connection between XCode / Developer Account / AppStore Connect / AppleID.
I've looked through other posts on this topic but most seem several years out of date, and I am aware that AppStore functionality in this area has changed over the years.
Any help would be greatly appreciated - particularly if you can recommend which route to go down and answer any of my specific points. I have tried asking Apple, but all I get back are standard replies directing me to their app transfer process - unfortunately though I'm something of a solo outfit and I really need the benefit of people's experience here, as I need this process to go quickly and smoothly!
Cheers!
This question could be a duplicate of this one - SO Question but that question was asked 2 years ago and didn't get answered. Also, there were many questions related to this issues even before, but they are outdated now.
So, I got invited to an Apple Developer account with a role of Admin and I don't see that team in Xcode, that person, who invited me has individual account. Moreover, I'm a member of other developer accounts and I can see them and use. But that accounts are of organisation types.
If anyone faced same issue - how can I fix that?
Simply logging out of account in Xcode and relaunching/restarting Mac didn't help.
I'm going to guess that what the account holder actually did was this (as described by the docs):
Individuals enrolled in the Apple Developer Program can give up to 10 users access to their content in App Store Connect. All users receive access only to App Store Connect and are not considered part of the team in the Apple Developer Program.
That sounds like exactly your situation as you describe it.
I have an existing project, quite old, with its own support system: in-app purchases, links on web pages, etc.
I would like to overhaul the app significantly front and back end, so much so that basically none of the original code will remain. Maybe even write it in Swift instead of Objective-C, mostly because it's getting harder and harder to find Objective-C documentation.
Is it possible to set up the new app in Xcode so that for all intents and purposes, the app store just considers it to be a new version of the existing app? The in-app purchases work with it, the links to the app store still work, etc.
Yes, no problem. As long as the new app has the same bundle ID as the old app (CFBundleIdentifier in the Info.plist), it is the same app in the eyes of the App Store and Apple. You can change everything else about it and they won't care: icons, user-facing name (CFBundleDisplayName), underlying language, interface, major functionality even. The in-app purchases are attached to that bundle ID so they just keep on working; the links to the app store won't change. You can start a completely new project, from scratch, and as long as the bundle ID is the old bundle ID, it's the same app.
TestFlight is a welcome change for iOS. It makes distributing beta versions painless for both the developer and the testers.
Does Apple support TestFlight for Mac OS as well? I've done quite a bit of searching and haven't found anything conclusive one way or the other.
We have an OS X app store app that turns out to have an install problem with Yosemite. We failed to do a first install test against Yosemite, so we missed the problem.
I developed a fix and would love to have some new users try it out. It's petty complex, difficult and disruptive to have current users delete the entire "container" directory and kill the preferences process in order to simulate a fresh install.
I also don't like the idea of distributing an unlocked version of our app. If that gets out, it could damage sales of the app store app.
I've done things like added an expiration date to a test app (weak protection) or created developer ID builds that will only run on machines from a specific list of MAC addresses. The last approach works, but it's tedious and painful to maintain, and requires that the tester give up uniquely identifiable information about their machines.
I'd really like the ability to create apps that will only run on beta tester's machines, like TestFlight does for iOS.
This is a developer question more than a code question. It isn't a great fit for SO, but I can't think of a better Stack Exchange site to post it. If anybody has a suggestion of a better site to post the question I'm happy to move it there.
This document at Apple Developer explains it.
It says you should register the testers' devices and generate a provisioning profile that includes them. Which means, theoretically, the app won't run on any device not in the list.
Here is the strange thing about it however: I have two Mac computers and I didn't register either of them with my provisioning profile (in fact the list of registered devices is empty right now), but I can run the exported app image on both easily. The app is sandboxed and signed, ready for App Store distribution, but nevertheless it runs on unregistered computers. It might be that with an empty device list it allows to run on any, or it might be that I'm doing something wrong with code signing.
I will update the answer once I figure this out.
Good news for everyone (including me) waiting for TestFlight for Mac - it just got announced on WWDC21.
Unfortunately, it might take another few months until it is out of beta and publicly available for everyone. But since this question is almost more than 6 years old, its just a fraction!
I"ll update the answer if there are more details available
Update
TestFlight on Mac will be available to download on the Mac App Store. It will be similar to the iOS version of TestFlight offering almost the same functionality to both developers and testers.
It supports both native Mac apps and iOS apps on Apple Silicon!
It is now available.
TestFlight is not available for Mac apps.
source: https://testflight.apple.com/
😕
Scenario
I have an app that I've been working on for 6 months. I have already made the app for native iOS and about to put it on the Apple App Store. I know that I will want to work on the Android version of the app starting soon, but I would like to "lock-up" the name of the app on the Google Play Store before I begin working on it. I would hate to work another 6 months working just to get to the end and find that someone else took that name.
Question
How do I save an app name on the Google Play Store for future distribution?
You don't need to, Duplicates of names are allowed in Google Play. :)