static framework

[xiaoyuting]

MAX SDK Version

12.4.1

Device/Platform Info

iOS 17

Current Behavior

we need a static framework

Expected Behavior

we need a static framework

How to Reproduce

we need a static framework

Additional Info

we need a static framework

[thomasmso]

Thanks for reporting @xiaoyuting. Why do you need a static framework?

[xiaoyuting]

I have always used static libraries, and used dynamic libraries to include static library compilation, and now changing to dynamic libraries will change the project compilation and access process, whether static libraries can be provided

[thomasmso]

@xiaoyuting - can you hardcode to v12.4.0 of our SDK? That is still static.

[MattFoley]

Thanks Thomas, I also use static libraries. I will attempt to hardcode to 12.4.0, as long as it still supports the latest iOS privacy manifest requirements.

Thanks!

[MattFoley]

Hi @thomasmso could you tell me a bit more about what changed in 12.4.1?

• Update SDK to allow Apple App Store Connect to be able to detect privacy manifest correctly.

I see this, but am unsure exactly what the ramifications of this are, and since I'd like to use a static framework, I would prefer to use 12.4.0. (I ship an SDK myself, so static frameworks are always much preferred over dynamic frameworks, as using dynamic frameworks can add extra overhead to our customers build and integration process)

[thomasmso]

@MattFoley - Since it's a static lib, our SDK will get compiled into your app's main binary. Thus, you have to declare the usage of User Defaults in you app's privacy manifest. You can check out our SDK's privacy manifest file as an example on how to declare.