- This topic has 22 replies, 5 voices, and was last updated 11 years, 1 month ago by
.
-
Posts
-
Web app is not triggering the MobiONE “Back” button; nor is the “back” arrow in the Safari browser being lit up.
This error is very inconsistent as it does work once in a while, then won’t work at all when the web app is reloaded.
Is this an issue, or is there some setting that we are missing to “force” the back button to work?
Thanks in advance for any advice on this issue.
You did not provide any device or os info. But my guess is the issue occurs on iOS7 fullscreen webapps (webapp saved to homescreen). See this discussion about iOS7 mobile safari bugs http://www.genuitec.com/support-genuitec/viewtopic.php?p=20619&f=2#p20619
If it is related to device/os other than iOS7 please share those details.
We are only looking at iPhone and iPads and the issue is present on both.
The < and > arrows on the browser are not lighting up, which then makes the “Back” button non-functional.
Could there be an issue with the back button function in MobiONE?
Hi herb200mph,
Can you share more details about OS version, are you using iOS7? Are you running webapps from the homescreen? Wayne identified some issues including the back button problem for ios7 webapps launched from the homescreen. Please share details and we can follow up once we have the info. Also what version of mobione are you using?
Operating System on both iPhone, iPad is the new ios7.
The apps are buttoned from the home screen and are cached. File size approx. 50MB.
Problem is erratic, mostly failing. The browser < and > arrows don’t light on page moves, which is also the same case for the “Back” button from MobiONE.
We have, on occasion, have gotten it to work after several reloads, but then, the next time, it fails.
the javascript that Mobi uses for BACK button is history.back(-1).
The history javascript object in ios7 is jacked up.
It will not work!
The workaround is to change the code to a transition SLIDE_RIGHT.
For pages that can be navigated to from several source pages (many to one),
the code has to be handled in javascript.
On click, set the UI to execute a javascript code. In the javascript code –
in the page-transition method, set a flag depending on the last from-page (e.g. 1, 2, 3 etc)Then when the onclick method is called, check this flag and then do a transition
to the appropriate caller page.Really?
All that coding/effort for just a “back” function? GAG!
Which still does not explain why, in 8 other web apps created in MobiONE, the “back” works fine in both browser window and for the MobiONE “back” button function.
We have actually copied a “working” app to this app, and the error persists.
So, the question remains: what is preventing the “back” function from working?
Or, what “could” prevent it from working w/o writing a whole bunch of code.
The web app contains 360 separate screens, so doing the code you suggested isn’t practical at all.
The navigation from pages to all other screens are somewhat complicated and not linear as an ebook for example.
Understood.
the BACK button, that is history.back(-1) javascript code will not
work in ios7 in webapp fullscreen mode.it has to be fixed in ios7.
Herb, Everest is absolutely right in what he says and for my part I don’t think Apple will be coming to the party anytime soon. In my opinion Apple only want native apps on their devices and have done this on purpose. I hope I am proved wrong. Turn your app into a native app and it will function ok and look better. Unless Apple make changes to iOS7 web apps are no longer a viable alternative.
One of the reasons we made it a “web app” is to not allow Apple to be the judge of the content, which isn’t any of their business. The apps are legitimate, and there will be hundreds of them when the project is completed, all nearly identical. These are business apps from my client to their clients, and we are not playing Apple’s game of having an Enterprise license with all their rules, which won’t work in the manner in which this is being done.
My Client – me, a non-employee developer, my Client’s clients, their employees.
That configuration simply doesn’t work with the way Apple has their rules about native apps.
Also, the apps are for internal client’s client use, not available to the public, neither free or for purchase.
I think we can create a JavaScript file for the “back” feature, and simply execute that script when the button is pushed and that will end it. Just a PIA to do that, but we may just have to undertake the task.
Will post any updates relating to the solution.
Actually, regarding the back script for web app full screen mode…
The apps are actually running in the Safari browser, so it should work with the proper script.
We shall see.
Herb, Sadly it’s not just the back button that has issues, read here:
http://www.genuitec.com/support-genuitec/viewtopic.php?f=2&t=6150Without an icon on the home screen of the phone you might just as well use Safari to connect to a mobile enabled website.
Actually, we “do” have the app icon on the Home Screen for each app.
Everything within the app works just fine, there are no inoperable parts of the 360 pages. It all works well.
Except, of course, the back button – but that isn’t consistent among the apps, re: several apps cached on the same device.
For some, the “back” button works fine, for others, not.
