Forum Academy Marketplace Showcase Pricing Features

Android Login not Working?

Hey everybody,

For some reason, users that are on Android are unable to login to their admin/mobile pages. I’m using the Google Nexus 6 as an example, and whenever I press the login button with the correct credentials, nothing happens: https://www.loom.com/share/22ddcbbdbd0746d0b5c094d19f590918.

Here’s the workflow:

  1. User clicks on top right icon to open pop up
  2. Pop up opens, login inputs show.
  3. When a user presses login, it should go to the mobile page (if they’re on their phone), or the admin page (if it’s larger than 750 page width).

This workflow works perfetly on iphones/laptop, but it seems like androids are not friendly for this - does anybody know how to fix this?

Screen Shot 2020-10-13 at 12.21.30 PM

Is the log the user in on a separate workflow than the “go to” actions? If so can you take a screen shot of them? Does that occur before or after your page redirects

Is it not some interaction of “stay logged in”? Maybe the redirects cause it to log the user out instantly? What happens if you set it to “yes”

1 Like

Hey Anthony,

Appreciate the questions. The login user is on the same workflow as the go to actions. I tried doing both (in terms of staying logged in and remembering the email), nothing happens still.

Here’s the link to the mobile emulator: http://mobt.me/rZxd

User: [email protected]
PW: Test55$

1 Like

I just tested it on my s10+ on android 10 and I was able to log in

Maybe the issue is with MobileTest.me??

Have you struggled with making it work on an actual android device you have? Or maybe you don’t have one and were using a virtual version?

I’ve got it working on my end! :smiley:

Here’s a video aswell!

Hey, really appreciate the video. For some reason tho, it’s not working on the person’s nexus phone, and this is what they see. Do you know how I can solve this?

I think that’s a cookies/cache problem. It looks like on this post some found success with clearing cookies.

I guess there’s some sort of cookie or cached file that detects The login date and time and it may just be using that and comparing it with the current date and time and seeing that it’s expired.

Here’s the post