Hi there,
I recently tried uploading my app (built with AppBuilder) for the first time to the Apple store. After reviewing the app Apple replied with the following:
I requested extra information from Apple what may cause this error, but they told me to contact Telerik for help instead. My app uses no custom plugins, only the standard plugins that Telerik has already provided. That means it's pure html/css/javascript. As the html is shown within a browser control inside a native app, my guess would be this has something to do with the tool itself.
If anyone has had this same problem before, please let me know how you (hopefully!) solved it.
Kind regards,
Aidan Langelaan
I recently tried uploading my app (built with AppBuilder) for the first time to the Apple store. After reviewing the app Apple replied with the following:
We found that your app uses one or more non-public APIs, which is not in compliance with the App Store Review Guidelines. The use of non-public APIs is not permissible because it can lead to a poor user experience should these APIs change. We found the following non-public API/s in your app:_canShowMIMEType:webView:decidePolicyForMIMEType:request:frame:decisionListener:I requested extra information from Apple what may cause this error, but they told me to contact Telerik for help instead. My app uses no custom plugins, only the standard plugins that Telerik has already provided. That means it's pure html/css/javascript. As the html is shown within a browser control inside a native app, my guess would be this has something to do with the tool itself.
If anyone has had this same problem before, please let me know how you (hopefully!) solved it.
Kind regards,
Aidan Langelaan
3 Answers, 1 is accepted
0
Hello Aidan,
This is a known problem related to Debug/Release configuration in Visual Studio, Publish wizard should always use Release, but as of now it does not and takes your current build configuration, which in your case must have been Debug. To remedy this problem, set manually your build configuration to Release, see this screenshot.
Regards,
Steve
Telerik
This is a known problem related to Debug/Release configuration in Visual Studio, Publish wizard should always use Release, but as of now it does not and takes your current build configuration, which in your case must have been Debug. To remedy this problem, set manually your build configuration to Release, see this screenshot.
Regards,
Steve
Telerik
Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)
0
Aidan
Top achievements
Rank 1
Rank 1
answered on 19 Feb 2014, 09:43 AM
Hi Steve,
Thanks for your reply, but I highly doubt we had the wrong configuration while publishing the app. This is something we rigorously check before publishing any apps or websites. I will try and make a new build, but expect to see the same result.
Regards,
Aidan Langelaan
Thanks for your reply, but I highly doubt we had the wrong configuration while publishing the app. This is something we rigorously check before publishing any apps or websites. I will try and make a new build, but expect to see the same result.
Regards,
Aidan Langelaan
0
Hi Aidan,
The non-public API that Apple reported is used as part of the LiveSync feature which is supported only in Debug mode, so you couldn't have built in Release, as Release build do not include the LiveSync feature.
Regards,
Steve
Telerik
The non-public API that Apple reported is used as part of the LiveSync feature which is supported only in Debug mode, so you couldn't have built in Release, as Release build do not include the LiveSync feature.
Regards,
Steve
Telerik
Icenium is now Telerik AppBuilder, and is part of the Telerik Platform. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)