App Rejected due to UIWebBrowserView Non Public API Usage

[sam-coley]

The latest version of our app has just been rejected by apple for the use of the Non Public API UIWebBrowserView which is used in this plugin.

We've been using this plugin for a while with no problems but it seems Apple are now onto the use of UIWebBrowserView.

Full message from Apple:

Your app uses or references the following non-public APIs, which is a violation of the App Store Review Guidelines:

UIWebBrowserView

The use of non-public APIs is not permitted in the App Store because it can lead to a poor user experience should these APIs change.

Next Steps

Please revise your app to remove any non-public APIs. 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 in future submissions.

Additionally, if you are using third party libraries, please update to the most recent version of those libraries. If you do not have access to the libraries' source, you may be able to search the compiled binary using the "strings" or "otool" command line tools. The "strings" tool can output a list of the methods that the library calls and "otool -ov" will output the Objective-C class structures and their defined methods. These tools can help you narrow down where the problematic code resides. You could also use the "nm" tool to verify if any third party libraries are calling these APIs.

[TheRocktopus]

+1

Just had an app rejected by Apple a half hour ago for the same reason. This plugin is the only place I can find UIWebBrowserView in my source.

Edit March 22: App has been approved with the latest update. Thanks!! :)

[mubasshir]

+1
I just came here to post but you posted already!

I investigated found out to be hackishlyFoundBrowserView is non-public API which is we are using.

[DimDrop]

Also had same issue today with app rejection due to using uiwebbrowserview non-public api.

[vijaydarkonde]

So Mubasshir, Have you found solution to fix it

[mubasshir]

For now I've removed plugin and submitted to store. Waiting for team to resolve. I suggest you guys to use older version if possible

[vijaydarkonde]

I have also remove the plugin and submitted back. App is now using default keyboard which is fine for my app.

[DimDrop]

Removed plugin and submitted for review. Using default keyboard without issue,

[diegodotta]

+1 Sad!

[vijaydarkonde]

My App is in review, I will keep posted.

[tony--]

This SO post has a different implementation that looks to do the same thing as UIWebViewExtension's hackishlyHidesInputAccessoryView, but it does not contain the string UIWebBrowserView.
I didn't test it, but it has a 15 upvotes and positive feedback in the comments.
Worth a look?

[mhartington]

Thanks for reporting this issues everyone. We'll take care of this ASAP!

[ghaiat]

+1

[rwvandenberg]

+1

[ravitejk]

+1

[tlancina]

Hey everyone, I've just published version 2.0.0 of the plugin, which removes the hideKeyboardAccessoryBar method for the moment. I also published it as 1.0.9, so it's within a valid semver range for people using config.xml to save their plugins. I think your app being rejected by the App Store takes precedence over semver semantics on this one.

@tony-- thanks for the link! Looks like if([[view.class description] hasPrefix:@"UIWeb"]) might get around Apple's static analysis (if that's what they're doing).

We'll add it back in once we can make sure that apps aren't getting rejected. There's no public API for removing the accessory bar as far as I know, so we'll also be more clear that this is always a danger.

To update, do

cordova plugin rm ionic-plugin-keyboard
cordova plugin add ionic-plugin keyboard

Thanks for your patience everyone, and sorry for the headache! ❤️