I've always used Google Chrome for Mac OS or PC to access eServices without any problems. However, it seems that for some reason Chrome for iOS does not work we'll with eServices. For example I can login into eServices, then if I click on Search Member, the browser will kick me back to the login screen. No problems if I use Safari instead. Anybody else experiencing similar issues? Any work around or solutions?
Thanks!
Get an android.
Quote from: usafaux2004 on May 29, 2013, 10:14:23 PM
Get an android.
The power of Eclipse is strong in this one...
Quote from: NIN on May 29, 2013, 10:19:46 PM
Quote from: usafaux2004 on May 29, 2013, 10:14:23 PM
Get an android.
The power of Eclipse is strong in this one...
I've known him too long, even if I haven't seen him since 2008.
Quote from: vento on May 29, 2013, 09:45:33 PM
I've always used Google Chrome for Mac OS or PC to access eServices without any problems. However, it seems that for some reason Chrome for iOS does not work we'll with eServices. For example I can login into eServices, then if I click on Search Member, the browser will kick me back to the login screen. No problems if I use Safari instead. Anybody else experiencing similar issues? Any work around or solutions?
Thanks!
had the same issue.
Hit the "Request Desktop Site". You will have to log in again, but works like a charm!
Muahhhhhaaaaaaaa!
Quote from: JeffDG on May 29, 2013, 11:47:27 PM
Quote from: vento on May 29, 2013, 09:45:33 PM
I've always used Google Chrome for Mac OS or PC to access eServices without any problems. However, it seems that for some reason Chrome for iOS does not work we'll with eServices. For example I can login into eServices, then if I click on Search Member, the browser will kick me back to the login screen. No problems if I use Safari instead. Anybody else experiencing similar issues? Any work around or solutions?
Thanks!
had the same issue.
Hit the "Request Desktop Site". You will have to log in again, but works like a charm!
Thanks for the work around. Annoying when Google has a bug. :angel:
Weird, it's working for me on Chrome for iOS. I wonder if we have the same version.