iPhone app rejection for using ICU (Unicode extensions)

Posted by nickbit on Stack Overflow See other posts from Stack Overflow or by nickbit
Published on 2010-03-11T19:00:36Z Indexed on 2010/03/11 19:04 UTC
Read the original article Hit count: 368

Filed under:
|
|
|
|

I received the following mail form Apple, considering my application:


*Thank you for submitting your update to ??µ??es?a to the App Store. During our review of your application we found it is using private APIs, which is in violation of the iPhone Developer Program License Agreement section 3.3.1; "3.3.1 Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs." While your application has not been rejected, it would be appropriate to resolve this issue in your next update. The following non-public APIs are included in your application: u_isspace ubrk_close ubrk_current ubrk_first ubrk_next ubrk_open If you have defined methods in your source code with the same names as the above mentioned APIs, we suggest altering your method names so that they no longer collide with Apple's private APIs to avoid your application being flagged with future submissions. Please resolve this issue in your next update to ??µ??es?a. Sincerely, iPhone App Review Team*


The functions mentioned in this mail are used in the ICU library (International Components for Unicode). Although my app is not rejected at this point, I don't feel very secure for the future of my app, because it relies heavily on the Unicode protocol and on this components in particular. Another thing is that I do not call these functions directly, but they are called by a custom 'sqlite' build (with FTS3 extensions enabled).

Am I missing something here? Any suggestions?

© Stack Overflow or respective owner

Related posts about iphone

Related posts about app