This might be an old issue already solved in `0.7.1` <https://kotlinlang.slack.com/archives/C3SGXARS...

# kotlin-native

[Yashar]

This might be an old issue already solved in 0.7.1 https://kotlinlang.slack.com/archives/C3SGXARS6/p1528475089000678 but I wanted to get another opinion from the community.

Our dynamic scanner has identified a use of private iOS API: Frameworks/Core.framework/Core: _unsymbolicated_function accessed _NSBlock within a KMP library module. Upon some digging, I came across this similar old issue on github with fix already merged. So my question is, has anyone else come across this? And if so, is this issue already addressed and have folks been fine publishing to App store without rejections?

[Yashar]

I think the source in question is here: https://github.com/JetBrains/kotlin/blob/3925b0527401b252bc2542b2f1f5627d9ad13cba/kotlin-native/runtime/src/main/cpp/ObjCExport.mm#L377-L382

[Yashar]

Hey @olonho , looks like you approved the fix for the private API usage issue, so I am hoping to get some insight. I am unsure why adding a method via category is considered as private API usage but this workaround is not?

[Yashar]

If Apple considers it okay, then I am too. Just want to make sure our app does not get rejected from publishing because we ignored the scanner finding.

[olonho]

cc: @svyatoslav.scherbina

[svyatoslav.scherbina]

have folks been fine publishing to App store without rejections?

We regularly check that Kotlin/Native-compiled binaries can be successfully uploaded to App Store.

why adding a method via category is considered as private API usage but this workaround is not?

Because that’s how Apple automated checks work.

If Apple considers it okay

It seems to do.

[Yashar]

Thank you for the timely response. I am less concerned with your confirmations. 👍