Original problem: My flutter app using the http package connects to a rest service to get the data needed. If I am connected via my modems wifi, the connection would fail (but not timeout) on the login attempt. The circular spinner would spin forever (tried for 15 minutes). If I connect using my router's wifi, or my mobile data, the connection is fine. The app logs in and runs correctly.
I created a web app to test and after trying a few things, I found port 443 was the problem. I changed the port on my rest service and the app and now 2 emulators and 2 physical devices all work perfectly during testing.
Then yesterday I published the app update to the Play Store and the App Store. I'm still waiting on the app store to approve, but testing from TestFlight worked perfectly on my iPhone.
Google approved the app quite quickly, but when I install the update from the Play Store, no connection at all works now. I have tried uninstalling and rebooting the phone (Galaxy S22+ running Android 13 and a Galaxy S8 running Android 9) but regardless of whether I connect using mobile data or either wifi, the login sits trying forever. The app does not crash, it just won't login and although there is a timeout on the login connection, it doesn't timeout.
What could be the difference between the test version which works great, and the version I build for uploading to the Play Store?
Related
my xamarin.forms app needs to get data from sql server and for this i used a rest api. i hosted the webservice on a remote server and tested the app on my android phone. it worked well. when i tried to test the app on iphone simulator using mac in cloud to pair my vs to a mac, my app couldn't connect to the webservice. my HttpResponseMessage.IsSuccessStatusCode returned false. i tried to reach my service by copying its url in safari in my iphone simulator but i got: your search didn't match any documents. any suggestions?
My application, built with Ionic 4, Firebase, Postgres, Nodejs, Express has a client side and a server side.
the auth is implemented using firebase, and some server logics is implemented using an heroku postgres Daas.
I deployed the server project (the nodejs express with postgres db) to heroku. it works well (tested in postman).
but when I enter the app via google play (app store),
It shows blank white screen, and nothing happens.
the app works locally on my android machine (tested with devapp), works in browser, the server is tested, and client is tested too.
the only thing that does not work is the deployment to google play
I am trying to access an app i uploaded on play store through google play console on windows and every time there is network issue. I cleared the cached files and cookies. i restarted everything.It's still not working on any browser(chrome, Firefox, int Exp). I tried on an emulator and my phone and it's working there. But
i want to access it on my computer.
While working with my app that require network access...
The Android 2.2 emulator's network connection stop working...
The net was working properly but after some time it did not respond on emulator,
while it was working f9 on my system...
I have cross checked the net connections and restarted with the emulator(even created a new avd ). But the problem remains same my net is not working on emulator..
I have also checked the connection with F8 key on emulator...
My app manifest net permission is enabled....
Finally After all I have myself found the solution of to the problem:
It's very common problem that must have been faced by most of android developers....
Recently, while developing an Android Application, I was faced with a situation that wasted 2 hours of my time. The issue was simple, my app was not able to access internet from the Android Emulator.
Initially I thought fixing the issue should have been straight forward, but life is not always that simple.
So what was the real issue because of which my app was not able to access internet? There are multiple reasons because of which this issue could occur. Hence, I decided to document my findings so that other could benefit from it.
There are two main symptoms of no internet connection on android emulator.....
**Only your app is not able to access the internet
**None of the apps are able to access the internet
Lets look at what are the reasons behind each of them.
Only your app is not able to access the internet
If only your app is not able to access the internet on the emulator, check if any other apps are able to access the internet or not. For e.g. you could open up the browser application, visit http://news.google.com/. If the page opens up correctly then problem lies in your app itself and its simple to fix.
Basically, your app needs the Permission to access the internet. This can be done by adding the following line just before the end of tag in AndroidManifest.xml file of your application.
Compile and re-install the app in the emulator and try to access the internet from your app. It should work!
What is the use of uses-permission tag:
Android application can request certain permissions so that they can function properly. Some examples of permissions are, get users location, make a call, access the internet etc. App has to explicitly specify this in the AndroidManifest.xml.
When end users install such an app on their device, the android OS will notify the user that, app is requesting certain permissions. If users are fine with that, then only the app will be installed. Else users can deny the permission and the app will not be installed.
This mechanism is Androids way of implementing security and users privacy!
This is the more tricky situation:
None of the apps are able to access the internet
Now this situation is tricky. There are two reasons because of which this could happen
Proxy server is not configured on the emulator
Incorrect DNS used by the emulator
Setting Up the DNS Server:
emulator.exe -avd 'android1.6' -dns-server 8.8.8.8
The android1.6 is your avd name I created an avd with name android1.6
So just replace android1.6 with your avd name.
Run this code in command prompt after setting the path to tools & platform tools of your android sdk
I have created a web application using the Google Web Toolkit that is able to receive some data by a mobile client via Http Post. The transmission of the data works well and also the server / client communication using GWT RPC is no problem at all.
However, I need to debug the webserver when receiving data from the mobile device. As I am using Hibernate and MySQL within the web application I do not use the Google App Engine. So if I deploy the web application in local host mode it is only accessible on the localhost:8888.
Now, if I send data from the mobile phone, I have to send it to the locally assign IP address as the localhost of the mobile phone emulator is not the localhost of the computer, where the web application is running. To ensure that everything works, I tried to do some posts outside the emulator (on the machine the emulator is running on). This works, but how can I post from the emulator to my web application?
How can I get access to debug my system? I've already tried to deploy the final application to a tomcat server and use remote debugging, but that fails too.
Best regards,
Florian
Well if I understand your question correctly, the real problem isn't debugging the app on the servlet, the real problem that you're looking at is debugging from a mobile phone. When the mobile phone hits your local network (I'm guessing you're pointing at 192.168..?) you are accessing the compiled GWT code that does not communicate with the debugger.
Put another way, when you debug locally using a browser, you are actually not running compiled GWT code, but instrumented code that is executed with the GWT Debugging Plugin, that happens to work exactly like compiled GWT code. (mostly). So while your local version has "?gwt.codesvr=127.0.0.1:9997" or the like, your mobile phone version cannot do the same, and cannot thus communicate with the debugger.
The best that I've been able to do is to use logging extensively. If you're using an iOS device and change the settings are your safari, it can output logs for you from mobile safari. Also, if you're using the Android debugger with a WebView app, you can attach a listener for log messages and then ferry them on to the ADB and view those in Eclipse. Definitely not as good as a debugger, but that's the best I've come up with so far, and if anyone has a better solution I would love to know it :)
Hope that helps!