I have a mobile app built using phonegap +qx mobile 3.5.
I have a page implemented using qooxdoo mobile which has a header implemented using qooxdoo controls. The content section of the page is loading from an external system using a ajax call which returns a string(html+css). The html has built in click handlers which are not firing on ios. The html works fine when loaded directly without qx.
This is an existing app in android and seems to work fine there. Can someone help me get this working on ios?
EDIT : I am using native scroll and not the custom scroll plugin.
I believe this problem is caused by the used scrolling method.
If you just remove the macro "qx.mobile.nativescroll" out of your config.json,
qx.Mobile detects itself whether to use NativeScroll or iScroll.
In version 3.5 that means, Windows Phone 8 and iOS7 are using the native scrolling.
Do not forget to rebuild after removal.
Related
I have a React Native application that uses a WebView to display a Highcharts chart. It was working for a while but out of nowhere it just stopped loading in Android. The only fix I could find was to disable Chrome and re-enable it. Which makes me believe there is something going on Chrome on my phone that's making it break. I see in the Android developer docs, the WebView has a destroy() function.
Is there a way I can call this function from my React Native app?
MMM the purpose of the question is unclear.
You don't want to display the webview ? don't display it , remove it from the render function.
You want to display the webview ? display it.
You want to have conditional rendering ? have it, it will destroy the webview or create a new one. There is a lot of posts of how to have conditional renderind in google.
My suggestion would be... update chrome. If it's already updated, go back to previous versions. If you have android 7+ i think you can change the webview provider in the developer options, if you can, change it to android system webview (you will need to manually install it from the play store). Don't use a native solution for personal device problems.
I can't seem to find an answer to this seemingly simple question. I have an app that i've built using the command line phonegap tools and when i start this app it opens up. i am using something called ios_sim (https://github.com/phonegap/ios-sim) which launches the app in the simulator and does not launch xCode (i don't quite understand why this is a feature, it seems like xCode has some useful tools)
Anyhow, my app is not functioning the same way that it does in the browser and i need to debug it. I have also already installed Charles to inspect the requests and i can verify that the correct data is coming from my API so my assumption is that there is some sort of javascript error in rendering the page (the page is partially rendered btw).
All i want to do is view the javascript errors. the same way that you would in the console if you were looking at a web page.
how do you do that?
You have to use Safari Remote Debugging with Web Inspector. See in the relating cordova docs how to do that!
I have a web site built as a web app that contains a single 'select' menu. The menu works fine and the options are displayed when viewed in a browser including Mobile Safari on an iPad.
However viewing the web app with Guided Mode enabled (http://support.apple.com/kb/HT5509?viewlocale=en_US&locale=en_US) which prevents access to some iPad features, the tag stops working and won't open. A regular link using the 'a href' tag still works though.
Does anyone know why this particular tag is not working?
I've run into this same issue. It appears to be an iOS bug.
jQuery Mobile had a bug reported for this issue here: https://github.com/jquery/jquery-mobile/issues/6806
They solved it by coding around it, using hidden divs that are enabled by Javascript (See their custom select menu examples).
I am in the mist of creating a mobile web app and have both meta tags
I have an iphone 5 on 7.0.4
When I click on a regular link like the one below it, opens up a mobile safari window and leaves the webapp. I also tried setting the target to _self and same behavior.
Sign in
I then used my ipad which was on 7.0.3 and it worked as should, not opening mobile safari on links. I think proceeded to update my ipad to 7.0.4 and the same issue as I had on my ipad.
Anyone ran into this issue and or knows a fix ?
Thanks
Since iOS 7.0.4 all links in WebApps open in Safari. As a workaround you can use Javascript:
window.location.href='text.html'
But remember that these steps will not be captured in history (so there is no ability to use Javascript like history.back() ..).
Alternatively, if you are using a menu in your web app, try to combine iframe and Javascript, you can change the content of your iframe with this Javascipt:
document.getElementById("frame").src = new_content.html
This will prevent your WebApp to open up links in Safari and stay in WebApp view.
While developing a phonegap smartphone application which runs on ios/android and bb v6+, im using a web service call to google maps and using tags for navigating through the application. I received an answer from apple with the following rejection message:
We found the following issues with the user interface of your app:
- Did not include iOS features. For example, it would be appropriate to use native iOS buttons and iOS features.
Additional user interactive features are needed.
My app has 2 buttons, one for searching and one to view the search results, both of which are non-native, html < button > tags.
Is it possible to use the native iOS buttons with a phonegap project, i.e using the search button (magnifying glass with word 'search' underneath), with a plugin?
Is it possible that my app was rejected for using a Google Maps web service call? if that were the case, i imagine the rejection message would be similar to the rejection message seen in this previous post
Any ideas/suggestions/guidelines would be great,
thanks
You could implement the NativeControls plugin. Judging by your screenshots a the iOS tab bar should work well with your app.
Not using native controls isn't a problem in itself. However, your app is too close to the appearance of a standard iOS settings page, which means that anything which doesn't exactly match that will feel broken.