Description of problem: While logged in I clicked on Identify and searched for Animals. It automatically searched in my default location, Sonoma County, California. I selected an observation, clicked “Agree” and got an error message,
“Request Failed
You need to sign in or sign up before continuing.”
I tried adding IDs to other observations via the Identify page but got the same error. I am able to add IDs as normal via the Explore page.
I find that sometimes if I have had the Identify window open for a while (more than a day) I need to refresh the page or it considers the session to have been timed out and I get this message. This is a bit non-intuitive because the Identify page appears to work as usual until I try to add an ID.
Yes, I see this not infrequently when keeping the Identify page (or I think even individual observation pages at times?) open for too long, though how long is ‘too long’ seems to vary quite a bit. Refreshing always solves it.
Same. I’ve seen infrequently when leaving an ID window open for a long time. I’ve always just assumed some sort of authorization timed out and refreshed and it’s worked again.
Just had this happen although I didn’t have it open for that long. I was wondering why the ID page was acting weird. Oddly, all my IDs were recorded though. But I found I was logged out when I went to my dashboard to try to fix the ID problems I was having.
Seems like a different issue. @dlevitis was not logged out, I believe, the token for that single page just expired. It sounds like you were logged out of your entire session in that browser?
Not entirely sure - I had a page of unknowns that I was going through, and I came back to it after a few hours. It seemed to be working mostly normal (except for one issue, noted below) because I was identifying, and all of those saved, but when I clicked away from that page, it showed I was logged out. It was really weird.
There was also something else happening that I thought was related to me being logged in but not really logged in, but it’s a separate issue that I’ll have to file a bug report for it it bugs me enough.
