uerceg
commented
6 months ago Hey @donuts-mineshima and the upvoters,
The challenge we have faced (and why Unity SDK 4.38.0 update is lagging a bit behind) is because the way how we are bundling native iOS SDK (just plain ol' .a library + public header files) && with the Unity's inability to simply allow us to drop Privacy Manifest file as a resource which Xcode will later understand that it belongs to our SDK, creating Unity SDK release which under the hood contains iOS SDK which has Privacy Manifest bundled inside would be a breaking change.
In case anyone is curious why, it would be because right now all your apps are built in a way that they have our .a library and header files linked to your app's Xcode project. Simple removal of those files from upcoming Unity SDK update would not work for 2 reasons:
- Unity IDE doesn't remove by default the files which new version of Unity plugin removes (it only adds new ones and modifies existing where it notices diffs). We unfortunately don't have any Editor script to monitor all the files during import of the new plugin version to potentially do this cleanup on our behalf. Even if we would be having this, issue 2 is there:
.aand.hnative files are already linked to your Xcode app project and those can't be easily removed unless manually. Sure, if someone decides to regenerate Xcode project, it would help and solve things, but there's probably a lot of users who are always appending changes when building. One can also argue that in some pre-processing scripts we could make sure to unlink not needed.alibrary anymore (and make existing.hfiles not to disturb the build process), but this can also have consequences in backwards compatibility within the current major version of the SDK (for the time being, downgrading Unity SDK is not that complicated process; these changes would make it a bit harder).
So a lot of tradeoffs for questionable gains having following things in mind:
- It seems that if one would specify app level Privacy Manifest and simply add Adjust Privacy Manifest entries there, that should "do the trick".
- We are getting closer behind the scenes to the possibility to ship next major SDK version update (v5) which would allow us to break things and where we will have the ability to include native iOS SDK under the hood so that it bundles Privacy Manifest file.
- So for the time being, we will release (today or Monday) Unity SDK v4.38.0 which includes native iOS SDK under the hood, but w/o Privacy Manifest bundled (whose options for the time being would need to reside inside of your app-level Privacy Manifest, but hopefully not for long time).
How does that sound to you?
With the release of Adjust's iOS SDK v4.38.0, support for Privacy Manifest has been introduced (https://github.com/adjust/ios_sdk/releases/tag/v4.38.0). However, it appears that the Unity SDK has not yet been updated to include this latest version of the iOS SDK.
When can we expect a new release of the Unity SDK that incorporates the iOS SDK v4.38.0? This update would allow Unity developers to take advantage of the new Privacy Manifest support and ensure that their apps remain compliant with the latest iOS requirements.
Thank you for your attention to this matter. We appreciate your efforts in keeping the Unity SDK up-to-date and aligned with the latest SDK releases for individual platforms.