search

chewnoill / medi-mouse

Meditech's Rat Trax for android
2 stars 1 forks source link

Network error #2

Open mlavoie opened 12 years ago

mlavoie commented 12 years ago

Upgraded to v1.141 yesterday. I like the new UI.

However, keep getting one of two errors. I should note that I have entered my corporate user name/password under settings.

The first is "There was a problem with your initial load". That appears when I click Sign In/Out, Find Person, or Refresh. That error appears for 3 seconds. I then get a second "Network Error: Request Aborted" error.

I'm running a Samsung Infuse (Android v 2.3.6) on the AT&T network. This occurs both on Wifi, and on 3G connectivity. Also happens when I'm connected to Meditech's internal Wifi.

I've tried deleting/re-installing app. Cleared cache as well.

chewnoill commented 12 years ago

Let me first explain a little bit more about what these error messages mean. As of 1.141 some of these messages have changed.

"There was a problem with your initial load" Before Medi Mouse (MM) can do anything it needs to load your stafflink (you can think of this as an internal way WebTrax identifies you as a user). This error indicates that there was a problem pulling this information from the WebTrax servers and MM won't let you out of this landing page until it completes this initial load (it should remember this information after the first initial load completes).

"Network Error: Request Aborted" There are a few different Network Error notifications you can receive, "Request Aborted" indicates that the network client was shutdown before it completed whatever it was doing. This will happen if you choose Refresh or reload your app while your network connection is still open. There should be a spinning mouse while network IO is going on. This error is probably the cause of the first error. It is also possible that your request it timing out, and if you wait a little while longer you may receive a message indicating that.

There are a couple things to try, unfortunately I don't think they will be significantly helpful to you:

  1. wait longer. There are a couple limiting factors that are out of my control when it comes to load times. The network your connected to and the WebTrax system itself are the primary bottle necks. For whatever reason, some users just take longer to load then others; if you are curious about this load time check out this website: http://www.meditech.com/employees/RATweb/RATweb.mps?TYPE=TraxFrame&User= However long this takes to load, it will take longer on your phone. I took the liberty of checking (based on your github username), it took 1.1 minutes to load up your information (as a comparison, mine takes just over 2 seconds). Not much I can do about that, MM will take at least double that time because it has to post twice.

2. While I have not been able to confirm that this is the problem, it might help you to remove some or all of the text on your trax; large amounts of text will add load to the server and the networks. While my app doesn't care about any of this text (yet), the server still sends it (if this works for you please let me know and I will start calling it an official solution). Does not work