Platform: IOS iphone
App version number, if a mobile app issue: 1.0.4
Browser, if a website issue:
URLs (aka web addresses) of any relevant observations or pages:
Screenshots of what you are seeing:
Description of problem: When I type out the name of an identification within the iphone app and select from the pop-up menu, the app consistently crashes and I have to restart. It does this every time I try to type out an ID, which is frustrating when computer vision does not pick up on a small insect or other detail that the user is attempting to identify. As an example, I took a screen recording and attempted to type in the ID for a forest tent caterpillar moth that I knew computer vision recognized, just to replicate the error. See attached screenshots, and if there is a way to attach the video instead, please let me know how and I will do so!
Step 1: Open up any observation that you would like to add an ID to.
Step 2: Click “suggest ID”.
Step 3: Click the search button in the upper right corner.
Step 4: In the text box, type the identification out. When the correct name pops up below the text box, select the check mark.
Step 5: My screen now shows “Something went wrong.” error message.
3 Likes
Thanks for your report.
I can see in the first screenshot tha you are starting this from the Explore tab.
Does the same also happen if you start from other screens, like e.g. from your own observations in the main observation list, or for other users’ observations from the Notification of Others tab?
I believe that the crash when starting this from Explore will be fixed in the upcoming version 1.0.5.
3 Likes
Thanks for your response! Just tried submitting a few example IDs from my personal observation tab as well as notifications for others. On my personal observation tab, tapping “suggest ID” then the search button, typing a name, and selecting it, all brings me to the “edit observation” page, even if it has already been ID’d by myself and others. Following the same process on my notifications for others, suggesting an ID and typing it in the search bar leads to the same crash/error I reported in my original post. If you’d like me to share additional screenshots of the error or anything else, please let me know!
2 Likes
I am also having the same exact problem as well for the past three days or so
1 Like
Yes, I’ve been having this problem for a few weeks. The error message suggested “we already know about this”, so I didn’t log it as an error. I’ve been working on the website instead, which is better for my muscles anyway. 
2 Likes
Thanks for checking some more. I have tested myself the route from Notifications of Others and I do not see it crashing anymore with the upcoming version. We hope to be able to ship it by next Wednesday after some more internal testing.
3 Likes
Version 1.0.5 has been released via the App Store, can you please try again after updating? It’s working for me, no crash.
1 Like
thank you for the update! i just downloaded the newest update from the apple app store and seems to be working for me as well, no more crash! :)
2 Likes