Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My conclusion, as of today, is that it is completely safe to replace the AppID prefix by a new one, with the exception of apps using the keychain. This opens up for migrating the prefix for all my exiting apps on the App Store to the new TeamID based prefix.</p> <p>This conclusion is based on the following input:</p> <ul> <li>A discussion I had with Apple's developer support a couple of weeks ago. They told me that there should not be any problems changing the prefix, except for apps using the keychain.</li> <li>A test I did, using ad-hoc distribution, verifying that an existing app on a test device did not lose any data when it was updated to a new version with another prefix.</li> <li>The fact that I have successfully uploaded new versions, with replaced prefix, of two of my existing apps without any problems so far.</li> </ul> <p>The status of the two "live" apps that I have changed, is that they have been approved in the review. However, they are currently waiting in "Pending Developer Release", since I am waiting for a third app to get ready in order to sync the release with that one.</p> <p>If I see any kind of problems when they go live on the App Store, I will of course update this answer.</p> <p><strong>Update:</strong></p> <p>The two apps were released successfully more than three weeks ago. The roll-out worked as expected and I have not received any user complaints.</p> <p>In summary, the answer is YES, this is completely safe!</p>
    singulars
    1. This table or related slice is empty.
    1. POIs it safe to change the AppID Prefix between updates?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMagnus
    1. USMagnus
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs it safe to change the AppID Prefix between updates?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCould you please explain how you managed to create new App IDs with different prefixes? It still doesn't let me do this. Says `An App ID with Identifier 'com.domain.appname' is not available. Please enter a different string.` - both for App IDs that I still have active and for the one I deleted while it was possible to delete them.
      singulars
      1. PO
      1. USFilip Radelic
    2. COThe option to create new random prefixes has been removed. If you start from scratch today, your only option is to use the TeamID as the prefix. If you have some existing apps using other prefixes, these existing prefixes will also appear as options when creating new AppIDs. In my case, I have only tested to replace an old wildcard AppID with a new explicit one using the TeamID. I think your problem might be another: BundleIDs need to be globally unique. See http://stackoverflow.com/a/6546206/824515 Perhaps it's not possible to replace an old explicit AppID with a new one based on the TeamID?
      singulars
      1. PO
      1. USMagnus
    3. COOne more thing: I have 5 apps on the App Store. None is using any features requiring explicit AppIDs. I had only one single wildcard AppID serving all apps. However, when I started to investigate this issue, I found that there were a number of existing explicit AppIDs on the portal that I have never created myself! There were exactly one ID for each of my existing apps. These were using the TeamID, even though my apps were using another prefix! Probably, these IDs were auto-generated when Apple introduced the new TeamID policy. It was one of these IDs that I used when replacing the prefix.
      singulars
      1. PO
      1. USMagnus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload