Posts by DecSoft

Hello Paolo,

In principle, there is no reason that causes than AB delete the project's file... please, remember that AB prepare some backups of our apps in the "_history" directory, so may this can help you in some way.

On the other hand, please, Paolo, provide me with a sample app in order to reproduce your problem, or, specify, step by step, how to reproduce it and I will try to do it.

Hello Tin,

Another possible approach is to do what I say above, but apply certain CSS code to the footer when your app run in the new iPhones. I say this in the case that you prefer something like that instead of change the "viewport" meta tag. Try both things if possible and choose the best.

Hello Tin,

The idea is to get a layout that can work in all the platforms and devices, also the new iphones. I know that this may requires changes in existing apps and in some scenarios (like apparently your case) can be more tricky, since the design of your footer.

Maybe a possible solution for your specific case can be to use viewport-fit="contain", like before, so your app continue working as before. Then, at runtime, you can check if the app is running in a new iphone, and if so change the "viewport-fit" to "cover".

I think this can be possible to do using a bit of Javascript code or the UserAgent action or the Device Cordova plugin.

With the below code you can change the viewport metatag to "contain":

Hello Tin,

Sorry, but, I am not sure if can understand. If you replace this:

... by this other:

Then you must see the "white band" in new iPhones, but not in the previous ones, if I am not wrong. That is, if you do the above change, you must get the same results that you get before.

Hello Tin,

The only thing you must to do is to edit the "index.html" and change "view-port=cover" to "view-port=contain". There is not possible to do it from AB, Tin, and probably is not a good idea... because the idea is that we design the app in a way that can work in almost platforms as possible. You no need to do anything else, however, nor touch any code: just change the "view-port". You may want to do it... until you try to adapt the app to the new used "view-port".

Hello Tin,

P.S: If, in the main while, you want to use the app with the "white bands", just edit the "index.html" file and set the "view-port" to "contain" instead of "cover". My recomendation, however, is that you try to modify the app to reach also the new iPhones: I invest yesterday a couple of hours to do this in some of my apps, but now it's working well.

Hello Tin,

I see your image. I am not sure if you are using the "Status Bar" in that project or not. Anyway, the footer is another kind of problem. If you try with the Calculator sample, for example, you can see twe don't have that problem. So maybe you must place the footer a little up in order to avoid the problem that you have now: depend what you use for the footer, you must do it in one or another way, but you must place the footer with enough space.

What we must take in consideration is this: with the "Status Bar" plugin we can reach the top of the app's view with any control and without problems. Without the "Status Bar" we need to leave enough space. And the same can be said for the footer, Tin: we must leave enough space for the footer, at least in some scenarios / apps... because not all the footers are the same.

I understand that this can be a bit tricky for you, but, that's the only solution if we want to be ready for the iPhones... without the "white band"... Some footers can just work like now, without changes... some others not.

If you look at the Calculator sample, you can see how I leave enough between the buttons in the footer and the app's view end. This is enough to deal with the new iPhones, that is, doing this, you can see the Calculator sample running as the above images.

P.S: If, in the main while, you want to use the app with the "white bands", just edit the "index.html" file and set the "view-port" to "contain" instead of "cover". My recomendation, however, is that you try to modify the app to reach also the new iPhones: I invest yesterday a couple of hours to do this in some of my apps, but now it's working well.

Hello Tin,

Yes; please, do it. Don't worry about Cordova. I can tell you that once you are ready with that and the other stuff, compile an app is quite fast and simple: even more in the recent versions of Cordova. Maybe there is some problem in the compilation of the app project in Windows... I try it here, and, the "Status Bar" plugin is installed as expected, etc. But, for some reason, apparently the plugin is not ready in the app.

Hello Tin,

That can be the problem. I am talking about compile the app in mac OS. I don't know why the compilation in Windows do not work. The main point here is clear: if you are using the "Status bar" plugin... where is the "Status Bar"?

That is the problem: apparently the plugin is not used for some reason, and that plugin must be used in our case.

Can you try to compile the app with Cordova in mac OS?

Hello Tin,

Apparently your iOS project is different that the files that I get here in my mac OS after compile the apps with Apache Cordova. Are you using the latest version of Apache Cordova and the latest version of XCode? Certainly, Tin, I can't say too much... because I can't reproduce the problem here! If you are using the "Status Bar" plugin, as apparently you are done, why the "Status Bar" don't appear and/or don't appear in the silver color? There must be something rare... because apparently you are not using the "Status Bar" plugin... for some reason (maybe you hide the "Status Bar"? I don't think so...).

That's is what I can see in your images: the "Status Bar" plugin is not present... and must be present...

Hello Tin,

Can you try with other app sample or one of your apps? Please, check that you use the Cordova "Status Bar" plugin...

Hello Tin,

Then I can't understand what can happen, since I can't reproduce the problem here. One thing is clear... apparently your app is not using the Status bar plugin, and they must do it... Are you try to change the color of the "Status Bar"? But we are on the same thing... the Calculator sample already set a color for the "Status Bar"! Can you see this, Tin? Can you take a look at the app's options -> Cordova -> Configuration -> Statusbar and confirm that you can see a silver color for the "Status Bar"?

Hello Tin,

Are you try with a new compilation of the app? Remove the "Compiled" directory, compile the app again. Remove the Cordova stuff of the app and compile the app again from the scratch. I can't reproduce that problem here, Tin, my above screenshots are from an iPhone X emulator, and, I also try with certain other app (a real app which I am developing) in the emulators of all the new iPhones and works as expected.

Hello Tin,

This is quite rare. I check rigth now the latest Calculator sample and they include the Cordova "Status Bar" plugin, but your Calculator sample apparently don't use it... maybe you need to start with a new Cordova compilation? Can you check if the app is using the Cordova "Status Bar" plugin?

Hello to all,

More information about this. I start to add a new "OpenWindowEx" action to AB when I fall into another question... yes; the "OpenWindow" action do not really use the "cordova.InAppBrowser.open", but the "window.open" method, in order to do their work.

I remember that in the past, the "InAppBrowser" plugin, automatically replace the "window.open" for their method, but, apparently this changes from sometime ago, and now we must do that explicitily by code, as we can see in the plugin's documentation.

This suprise me, because I can see that we are using "window.open", but this work like expected in certain Android app that I am developing! My doubt now is if I must change this... because maybe is not a good idea.

Let me to explain. The OpenWindow action, right now, relies on "window.open", works as expected, not only in Android, but also in all other platforms, including the web browser, because they no need to use any Cordova plugin.

So maybe it's a good idea to leave the "OpenWindow" action working like now. And, on the other hand, I am not to quite sure about the possible "OpenWindowEx" action, because this action must rely on the refered Cordova plugin.

Yes; some other actions relies on Cordova plugins, so, why not the "OpenWindowEx" one? Because I am not sure if this can be good, looking for the future. And more important... because we already can use the "cordova.InAppBrowser.open" without any problem, if we really wanted it!

Please, Tin, go ahead if you have any further question!