Mobile: Clicking Create New Account causes processing spinner icon to keep spinning


(Andrew) #1

I’ve tried multiple times to create new accounts on mobile using iphone 6 with Safari and I keep getting the same issue.

After I click “Create New Account” the spinner processing icon just keeps spinning and I can’t go anywhere on the app. After a while, I try clicking on the x to close the account creation form and when I try to go to the homepage, the page doesn’t load and I get a new spinner processing icon, so this bug seems to cause many issues. The actual account is created in the background (because the activation email is sent and everything will work from there); however, we’re launching a new forum using Discourse and this bug will prevent new users from creating accounts on mobile to access our forum as they won’t know that the account is actually created.

Has anyone else experienced this bug? I’ve tried it on multiple Iphone 6s and the iphone 6S and keep getting the same issue…


(Jeff Atwood) #2

Can you repro it here or on try.discourse.org? If not then it is likely a local configuration problem, not a bug.


(Andrew) #3

Yes I just tested on try.discourse.org and had the exact same issue. Here is a screenshot.


(Jeff Atwood) #4

I can’t repro this – I just created a new account on try.discourse.org (same code as meta) on my iPhone 7

I also got the signup email fine. Tapped the link and created the account.


(Andrew) #5

Thanks for the response, @codinghorror. We’ve tested on multiple iphone 6 (ios version 10.2) and it doesn’t work. As I said, the account is created in the background and the activation email gets sent, but after clicking Create New Account it just keeps spinning and nothing happens. Can any of your staff test with an iphone 6? We have to hold off on launching our forum as this bug will impact too many of our users. Everything else seems to work very well.


(Jeff Atwood) #6

There is zero chance this has anything to do with the phone. Have you guys customized your Discourse or done anything unusual regarding creating new accounts? We can’t repro any problem with a default Discourse install, and nobody else is reporting this.


(David Taylor) #7

Just something I noticed - @AndrewM’s screenshot of try.discourse.org does not have a padlock at the top (it does on my phone running the same OS).

Could some proxy be messing with the HTTPS and breaking POST requests? Is it through an enterprise network with some unusual setup?


(Jeff Atwood) #8

Very good eye :eye:!

Agreed, I suspect something upstream or downstream causing a problem.


(Doker) #9

Same behaviour here. Our site has had this issue for a while. I just tried on try.discourse.org and the spinner icon keeps spinning. Please see attached image. Tested on Safari, iPhone 6S (works on Chrome). It works on all other mobiles, including iPhone 4S and even iPhone 3GS.


(Andrew) #10

We have no customizations, other than css/html. Even after removing those, the bug is still there.


(Jeff Atwood) #11

We can’t reproduce. Do you have any plugins or unusual settings in your mobile browser?

I also noted your screenshot does not show the https lock icon. Are you visiting the wrong URL? I believe try can be accessed through both http and https so I strongly suggest using https so nothing can tamper with the requests.


(David Taylor) #12

I can reproduce by visiting http://try.discourse.org (not https) on my iPad - account is created (receive confirmation email), but the spinner just keeps on spinning.


(Jeff Atwood) #13

So the “bug” is that people are visiting the http version of the site? But how? I can’t even get to the http version. It’s enforced with HSTS.

Compare these screenshots

Notice padlock, meaning https.


(Rafael dos Santos Silva) #14
➜  discourse git:(master) curl -vv -L http://try.discourse.org/                                                                                                    
*   Trying 2001:470:1:3a8::201...
* Connected to try.discourse.org (2001:470:1:3a8::201) port 80 (#0)
> GET / HTTP/1.1
> Host: try.discourse.org
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Content-length: 0
< Location: https://try.discourse.org/
< Connection: close
< 
* Closing connection 0
* Issue another request to this URL: 'https://try.discourse.org/'
*   Trying 2001:470:1:3a8::201...
* Connected to try.discourse.org (2001:470:1:3a8::201) port 443 (#1)

How are ypu able to get http @david?

We do both 301 and https.


(David Taylor) #15

Interesting… I was on my University network when I managed to repro it - now I’m on my private network I get redirected to https. The university uses the same ‘eduroam’ network used across educational institutions worldwide, so I wouldn’t expect there to be anything too weird about its setup.

When I’m back on campus tomorrow (UK time) I’ll run the curl @Falco just ran and see what I get.


(Jeff Atwood) #16

Are you sure you guys aren’t being man-in-the-middle’ed for “security”? Because you are definitely not getting https.


(David Taylor) #17

I can’t think of any other explanation.

I reprod on an iPad connected to the enterprise wifi network. There are no ‘profiles’ or ‘certificates’ installed on the iPad, and AntiVirus/firewalls don’t really exist for iOS. So it must be the university proxying the connection and doing weird things in the name of security. Completely ignoring an HTTP 301 redirect does seem a bit extreme though.

It is surprising that so many people are seeing this issue at the same time…


(Joshua Rosenfeld) #18

To add some information, this isn’t eduroam itself - it must be network specific. Eduroam is just a system to allow users of any participating university to use their “home” University credentials at another University. It’s just authentication. Eduroam doesn’t redirect, rewrite, or affect traffic in any way. This issue must be “behind” eduroam.


(Matt Palmer) #19

Your campus network is definitely doing something funky, given that you can’t repro the problem unless you’re on the campus network. I would be interested in feedback from the other people reporting the problem as to what sort of network they’re on.

To try and run this down at our end, would anyone seeing this problem on try.discourse.org please include:

  • The exact (to the minute, at least) time the problem occured (preferably in UTC, but at least including a numeric offset timezone);
  • The IP address that the requests will be coming from (as reported by http://icanhazip.com/ or similar);
  • Your device’s details, including OS version, browser used (and version), and any plugins installed;
  • If you have tried to reproduce the problem on multiple devices, please provide the above details for all devices used, and whether it succeeded or failed for each of them;
  • A traceroute from your network to try.discourse.org would be very appreciated.

(Doker) #20

I just tried again.

  • I come to the https://try.discourse.org (padlock is there, ofc)
  • browse a bit, padlock stays
  • click Login, new window appears, click Create new account, padlock still on
  • enter info, click create new account, padlock is gone, keeps spinning

Time: 15:41 PST
IP: 64.46.0.223
Device: iPhone 6S, Version iOS 10.2, Latest Safari, no plugins

All other mobile devices work fine.