If your app still embeds web content using the deprecated UIWebView API, we strongly encourage you to update to WKWebView as soon as possible for improved security and reliability. WKWebView ensures that compromised web content doesnât affect the rest of an app by limiting web processing to the appâs web view. And itâs supported in iOS and macOS, and by Mac Catalyst.
The App Store will no longer accept new apps using UIWebView as of April 2020 and app updates using UIWebView as of December 2020.
I just submitted an update for my app to apple app store connect and received the following email message back⌠will this be fixed soon? âŚ
Dear Developer,
We identified one or more issues with a recent delivery for your app, âIWS VSAâ 1 (16). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
Weâre aware that Thunkers are seeing this message, just to draw your attention to two important things
First and foremost, everyone is still able to publish their apps to the app store.
Secondly, Apple themselves are yet to announce when they will stop accepting apps with this component. So, for the time being this isnât something to worry about, and when it does become a more pressing matter, weâll do the worrying for you!
Hello,
Does anybody know if to publish an updated version of my iOS App I have to complete the âPublishâ process all over again at the Thunkable portal ?
Thanks,
Carlos
I went with âPublishâ and uploaded all certificates etc created the first time i published and it worked fine. Confirmation reads: âCongrats !! ⌠wait for an emailâ.
This is what Apple responded:
Dear Developer,
We identified one or more issues with a recent delivery for your app, âSPAmeditationsâ 1 (6). Your delivery was successful, but you may wish to correct the following issues in your next delivery:
You can ignore this message. It is a message reminding developers that a particular API will stop being accepted by Apple some time in the future . We donât directly use that API but one of the libraries that we depend on do. We fully expect that that dependence will be removed soon, before Apple starts actually rejecting apps that contain it.
Hi all. So I am lead to believe that Apple is not going to continue with webview? When I submitted my app, this came up as a soon to be problem for my app.
Is there any knowledge out there as to what we need to do to replace this function? Thanks.
Hey there @L3on! Although I am not sure where to find it currently, in the past, I have read a post from @domhnallohanlon stating that we dont need to worry about this and that #teamthunkable will have this issue solved before the deadline.
I do wonder though:
will this update affect previously published apps (i.e. will they be taken down)?
as iOS continues to upgrade, will older apps utilizing the deprecated webviewer stop working?
can we receive an alert when the admins are able to publish this updated component to the platform so we may update our apps asap
what is the purpose of the update. what does the new webviewer do that the old one did not???
I have 1 last wonder. Will the webviewer handle URIâs or is this just an iOS issue?
on the topic of the functionality imporovements:, I have had issues in the past with things that could display on an android device but not iOS such as charts
In just over one weekâs time, Apple will begin rejecting new apps using UIWebView.
As far as I know Thunkable uses this - I read that there is an update in the works and just wanted to know if you will be ready when Apple is going to reject all new apps containing UIWebView?
The docs still just say there would be an update out before Apple/Android start rejecting such apps. Apple will start rejecting affected apps starting in April.