Post

Replies

Boosts

Views

Activity

Reply to Transfer of an App with Sign in with Apple Functionality
@DTS Engineer I’m experiencing a similar issue. Thank you for the clarification. Our situation is different from the original question because the app transfer has already been completed and accepted by the recipient team. Before initiating the transfer, we did not prepare the Sign in with Apple user migration or generate transfer identifiers for our existing users. We would like to understand what recovery options are available now. Our current situation is as follows: The recipient team has accepted the app transfer but has not yet released an updated version on the App Store. The production server, database, API domain, app Bundle ID, and existing application accounts remain unchanged. We had never created a Sign in with Apple private key for this app under the transferring team. The key was not lost or revoked; it was never created. The transferred App ID is no longer available in the transferring team’s developer account. Therefore, we cannot select it as the primary App ID when configuring a new Sign in with Apple key. We understand that the documented process requires the transferring team’s credentials to generate transfer identifiers. However, we are now blocked because we do not have a pre-existing private key and cannot select the transferred App ID to configure a new one. Could you please clarify the following? How can we complete user migration after the app transfer has already been completed? Since we did not prepare user migration before initiating the transfer, what is the supported procedure for completing it now? Can a key associated with another primary App ID be used for this migration? Can we create a Sign in with Apple key under the transferring team, associate it with a different primary App ID that still belongs to that team, and use it to generate migration credentials for the transferred app? In that case, we would keep the transferred app’s original Bundle ID as both the request’s client_id and the client secret’s sub claim. If that is not supported, how can we obtain valid transferring-team credentials? Is there a supported way to create the necessary credentials after the App ID has been transferred, or does this require assistance from Apple Developer Support? Is there a recovery procedure that does not require transferring the app back? If we are still within the 60-day migration period, can we resolve this without transferring the app back to the original team? If transferring it back is necessary, could you confirm the correct sequence of steps? We would appreciate guidance on preserving existing users’ access to their original application accounts before making any further changes to the app’s ownership or account bindings. Thank you.
2d
Reply to Transfer of an App with Sign in with Apple Functionality
@DTS Engineer I’m experiencing a similar issue. Thank you for the clarification. Our situation is different from the original question because the app transfer has already been completed and accepted by the recipient team. Before initiating the transfer, we did not prepare the Sign in with Apple user migration or generate transfer identifiers for our existing users. We would like to understand what recovery options are available now. Our current situation is as follows: The recipient team has accepted the app transfer but has not yet released an updated version on the App Store. The production server, database, API domain, app Bundle ID, and existing application accounts remain unchanged. We had never created a Sign in with Apple private key for this app under the transferring team. The key was not lost or revoked; it was never created. The transferred App ID is no longer available in the transferring team’s developer account. Therefore, we cannot select it as the primary App ID when configuring a new Sign in with Apple key. We understand that the documented process requires the transferring team’s credentials to generate transfer identifiers. However, we are now blocked because we do not have a pre-existing private key and cannot select the transferred App ID to configure a new one. Could you please clarify the following? How can we complete user migration after the app transfer has already been completed? Since we did not prepare user migration before initiating the transfer, what is the supported procedure for completing it now? Can a key associated with another primary App ID be used for this migration? Can we create a Sign in with Apple key under the transferring team, associate it with a different primary App ID that still belongs to that team, and use it to generate migration credentials for the transferred app? In that case, we would keep the transferred app’s original Bundle ID as both the request’s client_id and the client secret’s sub claim. If that is not supported, how can we obtain valid transferring-team credentials? Is there a supported way to create the necessary credentials after the App ID has been transferred, or does this require assistance from Apple Developer Support? Is there a recovery procedure that does not require transferring the app back? If we are still within the 60-day migration period, can we resolve this without transferring the app back to the original team? If transferring it back is necessary, could you confirm the correct sequence of steps? We would appreciate guidance on preserving existing users’ access to their original application accounts before making any further changes to the app’s ownership or account bindings. Thank you.
Replies
Boosts
Views
Activity
2d