Hello to all,
Here is a new DecSoft App Builder with the below changes, fixes and enhancements:
Hello to all,
Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:
Hello to all,
I hope you are all well. This post is to talk about the convenience to use the WKWebView engine instead of UIWebView engine for Apple iOS. These engines are "the internal browser" (in few words) in which our apps run in iOS. Apple is near to start to rejecting apps to be published in the Apple Store if they continue to use the UIWebView engine, but, this probably is not the most important reason to start to use the WKWebView engine in our apps.
The UIWebView engine works reasonably well, however, the WKWebView engine get our apps working more fluid and in a more consistent way with the modern browsers. One of the DecSoft App Builder platform are the modern browsers, and, what we wanted (always that is possible) is that our code works in modern browsers as well in iOS, Android and other platforms, without any code changes.
How to be ready with the WKWebView engine in our apps? It's quite easy! In your App Options -> Apache Cordova -> Configuration -> Extra XML textarea, place the below XML code, which applies only to the Apple iOS platform:
That's all! Save the changes, compile your app with AB and then with XCode, if everything is OK, your app is now using the WKWebView engine instead of the UIWebView engine and you and your app's users can enjoy the enhancements.
P.S. To see the above working, we must compile our app with cordova-ios 6.x (while I write this post using the latest version 6.1.0) and we must set the iOS "Deployment target" to 11.
P.S.2. The described above works in both the previous generation of DecSoft App Builder and also the current generation of the product. Remember, however, that the previous generation of AB is no more available, except for already customers. The current generation of DecSoft App Builder (which you can download from this website) is the recommended one for new projects.
Glad to know that you finally get it working! :-)
About the issue with the Sidebar, I am not quite sure that can reproduce the problem. I use the Swipe events of both the app and the view, and, apparently it's working as expected to show / hide the Sidebar. What I can note is that if we swipe to the left from the "grayed" part and "cross" the Sidebar, to say like that, then yes, the Swipe event appear to be not fired. However, this is apparently a default behaviour that we can't probably handle in other way. I think there is not too much trouble from the user point of view, since, for example, just by clicking the "grayed" part the Sidebar is hide... Anyway, if you wanted, please, send me a sample app via EMail and I will try to take a look.
About the adaptative icons, I am not sure if can understand the possible issue, since we are **only** following the Apache Cordova documentation for Android adaptative icons with images. Or I am wrong, or the "108dp" icons that you mention are not supported or at least not referred in the Apache Cordova documentation. So again, Michael, if possible, send to me a sample app (with the images that you are trying to use) and I will try to take a look here.
Maybe it's related with the Cordova version? Trying here with cordova-android@^8.0.0, I can't reproduce the problem, that is, I use a splash screen from an existing project in a new AB2 app, then prepare a release and everything works as expected. Maybe an update of Gradle can help here too.
Another point can be to take a look at the AB2 Program -> Options -> Behaviour -> Splash... trying to compress a bit more the used splash screen. Try to provide a more or less customized PNG splash screen too, for example, I use here 1024x1024 image of 442 Kb.
The Splash screen plugin used is the official one, and, it's included by default when a splash screen is provided.
The problem if you did not provide any information, is not only that you force me to start to deal with the plugin from the scratch, but, also, that I don't know the possible context, so, maybe my effort is non useful. This is common in support forums, Asley: we must try to provide as much information as possible about the possible error, so other people can try to help us in the best way.
Trying the plugin, I can get it working at the first time, without any remarkable problem. Below you can see a modification of the Camera sample app, which uses the plugin to crop the captured photo / image: copy the below code in a file like "Camera.ab" and then open it with AB1, compile it and finally try it in an Android device:
Everybody can read the DecSoft support forum for learning purposes, however only DecSoft customers can post new threads. Purchase one or more licenses of some DecSoft products in order to give this and other benefits.