Are you experiencing a technical issue with iNaturalist Next? This category is the place to report it. To report bugs with the iNaturalist website or other mobile apps, please go to Bug Reports.
Keep in mind that iNaturalist Next is currently at a stage where major development is still ongoing and it may be unstable. If you need a more stable version of an iNaturalist app, we recommend getting our current native Apple and Android apps.
By “bug” we mean that something is not working the way it is intended to. This is not a place to make a feature request, nor is it a place to start a discussion about how iNaturalist Next works. There’s a separate category for that.
-
Incorrect or missing translations can be fixed on Crowdin. See this page for more information.
-
Only one bug per report please.
-
You can also provide feedback directly to iNaturalist developers within iNaturalist Next by going to the side menu and tapping on Feedback.
When you make a new bug report here, you will see a template to fill out. This will help us investigate the bug, so please fill it out as thoroughly as possible. Thank you!
What happens next?
If a staff member can replicate a bug, they will make an issue on iNaturalist’s GitHub repo, where our developers will see it. When a fix is released, we’ll update the report on the forum and close the bug report here after forum members can confirm the fix works.
In order to make bug reports easier to sort and follow, we’ll try to use the following tags:
staff-can-replicate = a staff member can consistently replicate the bug, which is often crucial to fixing it.
github-issue-made = an iNat staff member has made an issue for the bug on GitHub.
staff-cant-replicate = iNat staff members cannot replicate the bug based on the details provided, making it difficult to investigate further and fix.
Things that will make a bug more likely to be fixed:
- it makes using iNaturalist Next difficult or impossible
- it affects iNaturalist Next’s core functionality or mission (e.g. posting observations)
- it affects many/all users across different platforms
- staff can reproduce it
- there is a safe, quick, and easy way to fix it (Note: things that seem safe/quick/easy may not actually be safe/quick/easy!)
- it can be fixed as a “package deal” with other related issues
Things that will make a bug less likely to be fixed:
- it is cosmetic or causes minor inconvenience
- it affects few users
- it can’t be consistently reproduced
- the fix is unknown or would be difficult/time-consuming
- fixing it would/may cause other downstream problems
- the cause is not iNaturalist (e.g. internet service provider, browser extension)