Hey All!
I wanted to inform you that Apple has announced a new requirement for all new apps and updates submitted to the App Store. Starting on May 1st, these submissions must include privacy manifests and signatures for commonly used third-party SDKs.
At OutSystems, we are actively working on a solution to streamline this process for our customers. We aim to enable customers to perform a simple native build, after which we will automatically add all the necessary information required for App Store submission. For customers using custom plugins with third-party SDKs, we will provide detailed guidelines to ensure compliance with Apple's new rules.
The following list of OutSystems supported plugins are impacted by these changes and updates will be coming to these plugins to provide the necessary privacy manifest changes over the upcoming weeks. As these updates are released, it is recommended that you update your projects to use the latest versions to keep your applications in compliance with Apple’s requirements.
In the meantime, for anyone looking to implement these new Apple rules immediately, we have a workaround available. Please refer to the attached PDF for more information.
Bumping. This post should be pinned for a while.
Hi,We have followed this workaround and seems we are getting error for android.here's the error log sample
Its weird why it was triggered an error for the PrivacyInfo on android?Here is the json we have added on the Ext. Config.
{"resources":{ "ios":{ "AppPrivacyInfo":{ "src":"www/PrivacyInfo.xcprivacy", "target":"PrivacyInfo.xcprivacy" } } }}
Any idea of this?
Cheers!
Was able to resolve the error after removing the PrivacyInfo file in the resource folder.Cheers!
Did removing the PrivacyInfo.xcprivacy file resolve your submission issues and allow you to successfully submit your iOS app? Thanks.
Hi everyone,
Has anyone else encountered this issue?
Let's say you have an app already available on the App Store/TestFlight, and the current version does not include a privacy manifest.
Now, you implement the privacy manifest in Service Studio and click "Publish".
From this moment until Apple approves your new build, there will be a mismatch:
• The App Store/TestFlight still holds the old version without the privacy manifest (since the new build is still under review).
• Meanwhile, the OutSystems build is now the new version with the privacy manifest.
As a result, when you launch the app, you get stuck with the following error message:
An error occurred while trying to update the app. If you want to retry the update, restart the app.
The corresponding error log states:
Upgrade failed – rolling back to previous application version. Aborting resources download. Failed to download resource {module name}/PrivacyInfo.xcprivacy?mKC0rGIVwWN+TNGw+Cv4Bw with error: (null)
Is there a way to avoid this mismatch period? Perhaps by forcing the OutSystems build to remain on the old version until Apple approves the new one?
Appreciate any insights—thanks in advance!