I am building an Ionic App and i have been testing the app on Google Chrome Canary and it was working perfectly fine as expected. Recently, i tried testing the app on Mozilla Firefox and the app was behaving a bit weird like some buttons weren't working and the app was getting stucked. I ignored it considering that it might be an issue with Mozilla Firefox. Today, i installed the app on my device and to my surprise the app is behaving the same as it was behaving in Firefox. Some buttons aren't working and also the app is getting stucked. I need to release the app for production, as early as possible and i am stucked with this weird issue.
Please help me out.
P.S. - I have also added the crosswalk plugin.
Related
I have developed an app in Laravel, and it works correctly, except when running from apple and android phones using chrome or safari. It returns error 419 and does not create the session. In the rest of browsers it works perfectly. This means that Laravel cannot be used for iphone?
I use Laravel 7.0, and the app works correctly except on apple phones with safari and android with chrome
Seems like a bug with "same-site" option, check out here: https://github.com/Fyrd/caniuse/issues/4813
I don't know very well the cause of the problem, but I see that the session is always created well except from the mentioned browsers. In this case the session file is not generated inside storage / framework / session.
I can not understand the reason why it only happens in those browsers and in the rest it does not
I am currently building a hybrid app using Ionic Framework. This app must support accessibility. In iOS, VoiceOver works great! But in TalkBack on Android, overall it works decent but having a few issues so I decided to try Crosswalk. In Crosswalk, Talkback seems to be working better. BUT, if the app pauses then resumes, elements are no longer high-lighted even though TalkBack is still on. Do you have any ideas how to resolve this? Does anyone else have this problem?
Thanks,
Chris
I have a weird problem with an App i'm developing with jQTouch and Phonegap. The App works fine most of the time, but sometimes (seems random) the App is stuck at the SplashScreen. Sometimes it still opens after a few minutes. It does nothing more than just load the HTML, CSS and JS files (no Ajax request or whatever). Is anyone familiar with this problem, or any ideas how to debug it?
Thanx!
Me too. I think we need to upgrade phonegap for our app.
I have a mobile app that's developed in mgwt and gwt-phonegap 1.8
It uses GWT-RPC, It works really well in iOS5 and all versions of Android.
In iOS6 the application works well only the first time.
Then if I start it again it appears that has cached the state from the previous session. (screens, values)
I have no mechanism to do that, and what's more the screens are dynamically created.
In addition, I have not used the mgwt linker that enables the application to run offline.
Anyone has an idea, what's causing this or how to deal with this problem?
Thanks.
It seems that the iOS6 webcontrol is caching the POST requests:
Is Safari on iOS 6 caching $.ajax results?
I started a GWT project targeted for iPhone (and later for other mobile platforms). Now there's a problem:
* I can use Safari on iOS to test it, but I have to compile my app which takes a while even after performance optimizations mentioned for example how-do-i-speed-up-the-gwt-compiler;
* I can NOT use Safari in gwt-debug mode to make quick tests without compilation Java to JS because there's no GWT plugin for Safari on iOS.
So: is there a workaround for fast test of GWT app on iPhone?
Same thing here. I have been developing a GWT app using PhoneGap to bring it to iOs and Android. I ended up just using Firefox for development, every once in a while letting the app run in the iOS Simulator (coming with XCode). But since the app is using geolocation via PhoneGap, there was no way around installing it on the phone every once in a while to make sure it behaves.
I found some mobile dev emulators, one that is coming to my mind is called Ripple. There are others out there, but non of them worked for me.