App store rejection due to usage of private API's which are not exposed via the public iOS SDK

[ManojAtamai]

_Kotlin_ObjCExport_initialize_block_invoke accessed _NSBlock from / System/Library/Frameworks/CoreFoundation.framework/CoreFoundation where NSBlock is a private API.

[ManojAtamai]

@simago Could you kindly address this issue?

[simago]

@ManojAtamai
I built a demo-ios app and checked the symbols, but I couldn't find the NSBlock.
How to check:

1. Build demo-ios to the simulator with Xcode.
2. Xcode menu -> Product -> Show Build Folder in Finder.
3. From the folder displayed in Finder, open Build/Products/Debug-iphonesimulator in Terminal.
4. Check symbols with the nm command:

$ nm ./SdkSample.app/SdkSample

[simago]

I found a description that NSBlock problem had been fixed in very old version of Kotlin-native.
https://github.com/JetBrains/kotlin-native/releases/tag/v0.7.1

[ManojAtamai]

@simago I am using SDK version 1.10.2. The Data Theorem security tool raised an issue, stating that the private API NSBlock is accessed in the initialization block.

[ManojAtamai]

@simago I believe the _Kotlin_ObjCExport_initialize_block_invoke method, related to Kotlin's interoperability with Objective-C, is invoking a method that accesses the private API _NSBlock. Could you please cross-check this?

[ManojAtamai]

Please find the attachment where we are getting the issue

[simago]

@ManojAtamai I found a reference to NSBlockin ObjCExport.mm of Kotlin/Native.
Please see lines 326 to 331.

Kotlin/Native adds a method to NSBlock class, but it does not instantiate NSBlock class nor call a class method.

[ManojAtamai]

@simago Could you please remove the reference to NSBlock so that our security tool does not raise an issue?

[simago]

@ManojAtamai ObjCExport.mm is a part of Kotlin, so I can not change it.