Hello,
We have updated our platform.
Please try the following: delete edited files on the Source tab and make Undo all source changes for the parent folder (if you have edited files). Select Cordova-ios version in the App Settings:
Hi Serhii,
I followed your instructions for adding the following line in the config.xml file: preference name="WKWebViewOnly" value="true"
When I submit the app to the App Store the error goes away. However, when running it on the phone from the App Store I just get a white screen. Since I am directly using the IPA I can not debug this in Xcode.
When I remove the line of code and resubmit the the App Store the app works as normal. (this was all done using TestFlight by the way).
Please advise; thank you
Hello John,
Could you please specify what kind of framework you are using for your app and do you have edited files on the Source tab (except config.xml)?
Hi Evgene,
The only file I have edited on the source tab was the config.xml.
Once to put the line of code as told by Serhii and I also changed this line as per the version bug:
ios-CFBundleIdentifier="io.appery.app.phoneApp" ios-CFBundleVersion="1.3"
Nothing else was touched.
I have no custom plugins etc
As the the frameworks see the pictures below:
Dear John,
We passed your issue back to our developers for additional investigations and we will get back with the update soon.
Hello,
Here is the update about the issue:
For JQM project we still see the issue, working on its fix. As a workaround please use the following instruction:
Select the latest InAppBrowser plugin (3.2.0)
Select a Cordova plugin "Cordova WKWebView Engine"
Add one more Cordova plugin: wkwebview-engine-localhost
see the example here: https://stackoverflow.com/questions/3...
pre<access origin="*" />
<feature name="CDVWKWebViewEngine">
<param name="ios-package" value="CDVWKWebViewEngine" />
</feature>
<preference name="CordovaWebViewEngine" value="CDVWKWebViewEngine" /> /pre
For Ionic 1 we have a solution:
Select the latest InAppBrowser plugin (3.2.0)
Add the following settings to the config.xml, according to
https://cordova.apache.org/howto/2020...
pre <preference name="WKWebViewOnly" value="true" />
<feature name="CDVWKWebViewEngine">
<param name="ios-package" value="CDVWKWebViewEngine" />
</feature>
<preference name="CordovaWebViewEngine" value="CDVWKWebViewEngine" />/pre
Build a new version of the app and upload it to the App Store
Ionic 4 applications should work without any extra changes
Hi,
I tried the above steps.
1) Select the latest InAppBrowser plugin (3.2.0) (see screenshot below)
2)Add the following settings to the config.xml (in the iOS platform section0 (see screen shot below)
3) Uploaded it to the App Store
When loading the app, first the screen shows the appery.io splash screen then the screen goes white as it did the first time I tried it with the previous instructions. (see screen shot below).
Subsequently, I removed the lines of code from the config.xml and kept the InAppBrowswer (3.2.0) checked, pushed it tho the App Store and now everything works.
But, of course, I still have the error from Apple about the Deprecated API Usage.
Any help would be appreciated
Thank you
Hi Serhii,
I've been trying to implement your suggestions with no success. If I implement the "Cordova WKWebView Engine" plugin, the apps navigation buttons and registering for push stops working. If I add the wkwebview-engine-localhost plugin, the app fails to build.
I have tried the changes to config.xml suggested by Appery and outlined here:
https://github.com/apache/cordova-ios/issues/661#issuecomment-599500855
I've been unable to implement any variation of the suggested fixes which works.
Thankfully, Apple has pushed back the deadline from 1st April until 30th June because of the pandemic , however, it appears that Cordova apps will not be accepted after that date unless this issue is fully resolved by then.
I would appreciate an update on whether a fix is in the pipeline.
I have shared the app with support. It's called Plas Coch (f5113da5-003d-4c16-8718-f3db6014775c).
Many thanks!
Chris
Hello,
We have checked it one more time. Here is the last update on how to make it work in JQM apps: