Non-poll creators see "Fetching poll" permanently

[ggordn3r]

As a regular visitor, no authentication, on my phone and laptop, I tried to vote in this poll: https://rankit.skelpo.com/vote/rDZnWYOUBh5BbaSUvF1b

It is Published and set to Open, Accepting Votes, so I should be seeing the "Vote" page. But when I try to view the vote page on my phone, I get a "Fetching poll" message permanently. I checked it on wifi and data, so I know it's not a connection issue.

Next, I tried to vote in this poll, which is Closed: https://rankit.skelpo.com/vote/11P9PU0oBcVS16P1fww5

It redirects me to https://rankit.skelpo.com/results/11P9PU0oBcVS16P1fww5/summary, which is good. However, on that page I also see a "Fetching poll" message permanently.

[proggeramlug]

Should be fixed!

[ggordn3r]

Issue still persists for me on this poll: https://rankit.skelpo.com/results/11P9PU0oBcVS16P1fww5/summary

[proggeramlug]

Good find - fixed!

[ggordn3r]

Hmm... now we're back to the situation I had at the beginning. On phone and laptop without authentication I am seeing "Fetching poll" permanently. I don't see the redirect to results anymore on the closed poll either.

update: I am able to vote on polls when signed in, even as a user other than the poll creator. So it seems to be an issue with the no authentication case specifically.

Console shows:

main.71097b8dad325d58d1c4.js:1 ERROR TypeError: Cannot read property 'uid' of null
    at t.limit_vote (14.2b2b63b2e64a0a60b622.js:1)
    at e._tapNext (14.2b2b63b2e64a0a60b622.js:1)
    at e._next (main.71097b8dad325d58d1c4.js:1)
    at e.next (main.71097b8dad325d58d1c4.js:1)
    at e._next (main.71097b8dad325d58d1c4.js:1)
    at e.next (main.71097b8dad325d58d1c4.js:1)
    at e._next (main.71097b8dad325d58d1c4.js:1)
    at e.next (main.71097b8dad325d58d1c4.js:1)
    at e._next (main.71097b8dad325d58d1c4.js:1)
    at e.next (main.71097b8dad325d58d1c4.js:1)

[proggeramlug]

Reload, I just verified through a private browser window that the original issue has been fixed. However I think the problem you are facing is introduce because your devices have some (normal) caches that are not using th enewest version.

[ggordn3r]

No good. I tried the following, any of which should eliminate the possibility of it being a cache issue: 1) I force refreshed the cache in my regular window, no effect 2) I opened up the links in a private window (screenshot below), no effect 3) I manually deleted my cache and cookies from the last 4 weeks and tried again in both regular and private windows, no effect

[proggeramlug]

Oldest error in the history of programming :D Your link above is not the same poll as the one in your screenshot. I typed the ID from your screenshot and was finally able to reproduce and then fix the problem :)

Good find!

[ggordn3r]

Whew! Glad you figured it out. Just checked and both the ones I tested before are working as expected.