I am encountering an issue after transferring an app that uses the FamilyControls framework to a different app account. After releasing a new version of the app post-transfer, the following problems arose:
- ApplicationTokens obtained in the pre-transfer version no longer function when used with
ManagedSettingsGroup.ShieldSettingsin the post-transfer version. - Using the same
ApplicationTokenswithLabel(_ applicationToken: ApplicationToken)does not display the app name or icon.
These issues did not occur in the pre-transfer version and everything worked as expected. We suspect that ApplicationTokens obtained prior to the transfer are no longer valid in the updated app released under the new app account.
We are seeking guidance on the following:
- Is this expected behavior after transferring an app to another app account?
- What steps should we take to ensure that ApplicationTokens obtained before the transfer remain functional in the post-transfer environment?
- If these tokens are invalidated due to the transfer, what are the recommended procedures for regenerating or updating ApplicationTokens for existing app users?
Maintaining a seamless user experience after transferring the app is critical. We would greatly appreciate any insights or guidance. Please let us know if additional information or logs would assist in investigating this issue.
Thank you!