I'm currently facing an issue trying to publish an update of my app in the Apple store.
When the app tries to connect to the API, the loader spins indefinitely.
When I test my app in all conditions it works perfectly.
I tried my app :
with different IOS version (including the 14.1 of IOS),
in debug mode,
in release mode,
with the testFlight app on an Iphone device
I also tried the connection with a VPN to check the server connection from another location
Moreover, I didn't change anything in my code that could alter the connection between the app and the server.
The app also works perfectly on Android.
The problem was solved making appeal of the reviewer's decision ... The app was totaly ok ...
I have same issue too. I tested my app all the way like you said. Also test with NT64 Internet Sharing too and i haven't get any issue like Apple said. They can't connect our api.
Related
Faced this situation:
The application uses localStorage to save user settings.
When saving, data is written to localStorage. I can even read them from there, everything is correct.
But at the same time, if you close the application window, and then open it again and log in as the same user, the data is not saved.
I see this error only on Windows (tested on Windows 10) and only when using Electron.
If I open the same application in a regular browser, the app works fine (saves and loads without any issues).
Everything also works fine on a Mac (both Electron and a regular browser).
Has anyone encountered similar behavior?
I would recommend treating an Electron app as a desktop application rather a web browser. Explore using node's file system API fs to store user settings.
I have the following problem:
I created a simple chat app with the this system as core (https://github.com/kishorekumaru/ChatSystem__Sample).
Now I started this app on a debain server and on the desktop it works perfectly but when I opened the page on my Adnroid device and started Google Chrome brwoser, the page shows up but when I want to enter something it doesn't do anything.
There is also no data displayed.
I think that the Android browser can't connect to the databas.
But why?
My server.js file is the same like in the Github rep. (see above).
I only added new styles and a button to send the messages so far.
EDIT 1
I tried debugging it with Google Remote Debugging (https://developers.google.com/web/tools/chrome-devtools/debug/remote-debugging/remote-debugging#remote-debugging-on-android-with-chrome-devtools) then it works as designed, when I unplug the cable it crashes again....
Best regards
Tobias
I am building a hybrid app, with AngularJS, Cordova, Restangular ond client side and Python with wsgiref.simple_server on server side. I am not doing anything special, this is very simply requests like this:
Restangular.one('/devices').get().then(function (response) {
viewModel.devices = Restangular.stripRestangular(response.devices);
});
I set baseUrl for Restangular:
.config(function(RestangularProvider){
RestangularProvider.setBaseUrl('http://192.168.54.102:8000/');
})
And when I use it on local computer with Chrome browser, everything is fast, works normal. But when I use it on Android on Phonegap developer app on device or install app on device with Android, it works crazy slow. It looks like it is send to server with big delay, cause it takes some time as I see debug server log on server side. It occurs also when python application with server is not in debug mode, for example when I start it normally after install on local computer. As I see some people has this problem, does anybody found a solution or a reason, which causes very slow HTTP requests in hybrid application? Thank you in advance for every answer.
Since you are a hybrid developer, I am sure you are familiar with the Chrome DevTools. For me on a Mac, hit cmd + option + i, or go to View -> Developer -> Developer Tools.
The really great thing about Chrome in recent history is it now works with Android WebViews too. Hybrid developers haven't always had this convenience, and had to debug essentially handcuffed using tools like Weinre.
Now we can use the DevTools directly in the Chrome browser while your Android device is connected by ADB from a new tab calling chrome://inspect
Here is some more detailed information on how to do this if you get stuck.
From here open up the network panel and see how long your requests are taking. If they are showing a significantly longer amount of time to load here, the issue has nothing to with Angular, Cordova, Restangular or probably even Hybrid architecture at all. I would check your network and performance elsewhere on the device.
If this is definitely not the issue, I would use the Timeline tab in the DevTools to see what is taking so long between your browser receiving the information and your device displaying it. If there is any significantly longer process taking place in between, you will see it here.
From previous projects I know that Apple's Captive Network Assistant (aka WISPr client, too) runs a restricted browser, see How can I debug the browser in Captive Portal? and Ajax on Captive Network Assistant on iOS and OSX.
My hotspot is running a angularJS web page. On a Windows Phone 8.1 and an OS X Lion my angular page works fine. On my iOS 8.3 there must be a JavaScript error somewhere in the code, because I can see the angular variable expressions {{myVar}} in the code which means the angular framework isn't loaded properly.
Any idea what could be the cause?
Solved
Cause has been found, not by me but a friend of mine. Turns out that the CNA browser (WISPr client) doesn't allow the use of the browser's local storage. Whenever you try to write some data into the local storage, the application crashes.
Thus, the solution is either to switch from local storage to normal cookies or to do a user agent detection in JavaScript and exclude CNA browser (WISPr clients) from the use of the local storage.
Many thanks #chedabob, the idea of checking if JS is enabled led to the local storage check. Really appreciate your support.
You could possibly use WeinRe to remotely debug it, however if the root of your problem is the Captive Portal view isn't running Javascript, this probably isn't going to help
https://people.apache.org/~pmuellr/weinre-docs/latest/
I have written a phonegap application, and it performs a pretty simple task, it gets some JSON from a YQL link, and then displays it nicely to the user. This works excellently when I run it using Google Chrome on a Desktop, but, my client tells me that it does not work on his device which is Android 2.3. What can be going wrong? I'm using phonegap build to build to app, and they tell me that it is given internet permission, but, when my client puts the APK on the phone (its not on the market yet), does he need to do something special for it to access the internet?
Thanks a lot,
Dhaivat
in phonegap, allow external host : Open phonegap.plist -> external host and add your url or * to allow all
within the phonegap app the webapp runs under the file:// protocol - this might affect things.
you should test this at least on an emulator yourself - clients usually screw up anything some might screw up when testing ;) best would be to test on an actual device tho.
I'm not sure if this will help but I had a similar problem testing my app here:
https://stackoverflow.com/questions/17496104/json-wordpress-feed-not-appearing-in-android-studio-emulator-using-phonegap
I needed to change access origin to ="*"/ in my config.xml