Android app keeps going back to display the previous screen, to the point where it's borderline unusable :(

Bug Reports
1

Platform: Android, version 16

App version number: 1.36.8 (628)

Phone: Pixel 8a

Screenshots of what you are seeing: https://youtube.com/shorts/PDGHFUDEsp8

Description of problem:

Step 1: Open iNat app

Step 2: Tap on the hamburger menu in the top left

Step 3: Tap on “Activity”

Step 4: Phone screen momentarily turns white, then returns to the previous screen. So if the clickstream is hamburger menu > Activity, the app will zip back to the home screen. If I’m fast, I can squeeze in a few more taps, but no matter what, wherever I end up, the app will always go one screen back. For example, if I go to Activitiy > [any observation] > taxon page, it will zip me back to the observation.

See the video that I’ve linked to. The only time that I hit the back button in that entire recording was at 43 seconds. Every other time it’s the app doing it by itself.

This makes it basically impossible to review IDs and comments on my observations. Which makes me sad.

It’s worth noting that this only seems to happen if I start from the Activity screen. I seem to be able to access everything else without issue. But any time I go to the Activity screen I see this. For example, if I go Explore > [random observation] > taxon page (for the taxon of the previous random observation) > View Observations > hamburgeer menu > Activity it’ll sit on the activity page for a second and then xzip me back to the taxon page.

Occasionally I’ll see the “iNaturalist keeps stopping” pop up, probably about 25% of the time.

Solutions that I’ve tried:

  1. Restarting the phone. Issue persists.
  2. Uninstalling/reinstalling the iNat app. Issue persists.
  3. Updating the phone’s OS: Issue persists.
  4. Shutting off my launcher app (Nova Launcher): Issue persists.
  5. Uninstalling/reinstalling the iNat app (post OS update): Issue persists.

This seems to have started today, and there’s nothing that I’m aware of that changed in any substantial way. No app updates, and no OS update until after I noticed the issue (hoping that, on the off chance, updating the OS would resolve the issue). I’m on iNat fairly frequently and I’m pretty sure I would have noticed this right away. Is it possible that it’s related to a server-side change on June 16th or early in the am on the 17th?

I’ll send the debug logs in a moment, and include a link to this thread in the email.

Thanks for taking a look!