Thanks all for reading my post. A bit of context: We just finished an app transfer to our developer account. We successfully signed and generated the new release. We are already able to roll it out in testflight were we found an issue. We store valuable data in the Keychain like Authentication tokens, once the new app is installed over the old one we are experiencing a loss of all data as the keychain become "untrusted". This is worst case scenario for us because all users will immediately lose the access to the app and hence the whole system. Questions: Is there a way to solve this issue, something like migration of the Keychain data? We came to know the standard migration path: Release a version that copies items from the old access groups to a new group based on com.apple.security.application-groups (App Groups). Wait for most users to update and run the migration. Then perform the App ID prefix change. Is this still the best method? Any improvements or new tools available since the 2022 DTS post? The problem with this is that the app is already on our account and that might need to rollback the transfer. Right? How long should we realistically wait for user migration before making the prefix change? Is there a way to measure migration completion? Thank you in advance!

Hello, Our Apple Developer Program membership is active and renewed until 2027, and the updated terms and conditions were accepted a few days ago by the account holder. However, in App Store Connect we are still seeing the following messages: "Your Apple Developer Program subscription has expired. Your apps won't be available on the App Store until you renew it. To renew the subscription, the account holder must go to the Membership section of their account on the Apple Developer website." "The Apple Developer Program license agreement has been updated and needs to be reviewed. To update your apps and submit new apps, the account holder must log in to their account, review the updated agreement, and accept it." Both actions appear to have already been completed, but the warnings are still displayed in App Store Connect. Has anyone experienced a similar issue? Is there any known delay for the system to reflect the updated membership status, or any additional step that we might be missing? Thank you.