Unable to access My Content on iOS

Platform: iOS

App version number: Version 1.0.2 (161)

Description of problem:

When I try to access “My Content”, it says “Something went wrong” and no content is displayed. This has been happening for a couple of days now (it worked fine previously). I downloaded the most recent version of the app last night but still no content.

Platform: iOS new app

App version number: 1.0.2 (161)

Screenshots of what you are seeing:

Description of problem:

The app has been giving me a Something went wrong error in the ActivityMy Content feed for the past several days. I have restarted the app, logged out and back in, updated it, and restarted my phone but none of these have made a difference.

The Following feed is unaffected.

I don’t know how to reproduce this, it just happened one day.

2 Likes

Yes, this is eactly my issue as well.

1 Like

I’ve gotten this intermittently in the past. I wasn’t able to do anything about it, and it simply went away on its own after about half an hour each time. This does sound more severe though…

1 Like

Oh hey, I was just filling out a report on this issue. Copied the info below, seeing as I’d already filled it out.

Platform (Android, iOS, Website): iOS 18.4.1

App version number, if a mobile app issue (shown under Settings or About): 1.0.2 (161)

Browser, if a website issue (Firefox, Chrome, etc) : N/A

URLs (aka web addresses) of any relevant observations or pages: N/A

Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):


Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.): When I open the iNaturalist app, there’s a red dot on the activity icon. When I click on it to review the notifications, it takes a few moments to load then gives me the message “Something went wrong”. For a few days it was restricted only to the “Following” notifications, but now the same thing is happening on the “My Content” notifications. This issue seems to happen regardless of how strong my internet connection is at any given time. Everything else within the app loads normally. I have tried force quitting and restarting the app, as well as updating the app. I’ll admit this isn’t a huge issue, it’s mostly just annoying and I was wondering if it was happening to anyone else.

Step 1: open iNaturalist app on iPhone

Step 2: click “Activity” bell icon

Step 3: wait for page to load. Message “Something went wrong” is displayed on the screen.

Step 4: click on “Following”. Wait for page to load. Message “Something went wrong” is displayed on the screen.

1 Like

Hmm, I’m not seeing this on my device, but we did get an email from someone experiencing the same issue. If someone experiencing this can email us a log file, that would be helpful.

  1. Go to the About screen
  2. Tap on the version number a few times until the see a pink “turn off debug mode”. This means debug mode is on.
  3. In the side menu, tap on debug mode.
  4. Tap on Log
  5. Tap on email log. Please write a note as to which the problem is when e
  6. You can turn off debug mode in the About screen.

I just sent one, thank you!

Great! We have a few now, I doubt we need any more. Our engineers will see them this week.

Via email, someone said this happened after they updated the geoprivacy setting for some of their observations. Did any one here experiencing the problem edit the geoprivacy of any of your observations?

Yes, I believe so, I have had this problem for about a week now

1 Like

Yes, I edited the geoprivacy of some of my observations via the webapp (not the phone app).

1 Like

I haven’t had it happen recently, but now that you mention it, I think this occurred after I changed one observation’s geoprivacy to Obscured.

1 Like

I have not made any geoprivacy changes.

Mine started working again today

Thanks for letting us know! We just released some changes on our server side that we think should fix this. Is anyone still seeing it?

1 Like

Were the obscured observations the cause of this problem?

No, it was a change on our server side.

1 Like

This topic was automatically closed after 16 hours. New replies are no longer allowed.