Hi Maryna,
as I said its intermittent and still failing here,
it doesnt fail every time, but has failed at least 8 times today already.
What code do I need to add an alert in mapping?
I'll say this again, when the login page opens the spinner sometimes runs for a long time and other times it will spin once and disappear
when the spinner spins for a while this is when it seems to fail.
In mapping to username and password fields add JS prealert(value);
return value;/preto see what values are passed to the service.
Hi Maryna,
Cheers for that bit of code, I added it, and it showed the correct login every time, so I believe that sorts out the possibility of wrong user or password.
I deleted any other js code on login screen and also deleted the splash screen that I intended to use for web app. So nothing is running on the login screen when it loads apart for code for the resizing of the image at the top of the page.
But still the login is failing.
If you load it on your iPhone, it will login, and login again, and again.
But leave it for a few hours and the spinner on login screen starts to spin longer more often, not every time, but enough to make it not login.
I totally understand you guys can't do our testing, this is what I am trying to do and explain my results to help to find a solution.
There's something wrong with the loading and login with this app, with the spinner behaviour it looks like js error, but no errors anywhere, firebug,wienre,safari developer tools.
I have a app in the App Store built almost a year ago, login is perfect, spinner on login screen spins for half a turn, this app has the same code and events used in This one but it's working.
So I can't find the end to this issue, I really hope you guys have some hidden secrets to find a solution.
Sorry for being so long winded, but I'm going bald here:)
Thx
Hello!
On all events of login service try to add alerts and check what events are triggered. On complete event show with alert prealert(jqXHR.responseText);/pre
Thanks Maryna,
I will do that
Hi Maryna,
here is an update
The error being returned with above code when login fails is "login not defined".
I went back to builder and stripped everything that wasnt being used, more css, images and js, reduced the app size a fair bit,
testing so far is much better, failure reduced.
we will keep testing and update tomorrow.
thanks alot
Hi Maryna'
so far the messages returuned on failure to login are "login not defined" and "login.html" s/s attached, its better but not solved
Hello!
Could you clarify what do you mean on "login not defined". The only one alert you get is the one on screenshot? So jqXHR.responseText value is empty string? What happens if you click on login again? Is there the same error? After error login start working on 2...3...10 time, or if error had occurred it doesn't work anymore?
Hi Maryna,
when login is successful the _id and token are returned in alert
"login not defined" was returned once in the alert.
"login.html" as screenshot is the alert that is returned on failure, if I click back and login again I get the same error.
Now I force quit the app,
it will take between 3-6 attempts to get success on login,
you can see its going to fail as the spinner spins a quarter turn and stops, you know this will fail.
once it has been successful it will login consistently many times.
close the app and leave it a while and when you try to login again it will often fail.
After being left alone overnight it will fail in the morning.
Its very inconsistent
Could you create simple test app with one screen and login to the same DB. Add alerts on success, fail, complete events to see what happens. Test on the same device which you use to test main app. Does it behave the same way?