Platform: iOS (iPhone 11 using iNaturalist: Next App)
App version number: (assumedly) 1.0.19
Bug #1: Blank Observation Bug
When batch uploading, some queued observations will appear entirely blank, requiring you to flip between neighboring observations in the queue and back to it multiple times before it’s fixed. This used to be significantly more prevalent before this newest app version, but it’s still present and still impactful. It happened roughly 4 times in this batch, on observations that had more than one image. Waiting for the blank page to load didn’t work - only flipping to and from to “reload” it (I guess?) https://youtube.com/shorts/V8x6c34UzZ4?feature=share
Bug #2: Identification/Taxon Search Screen “Jittering”/“Stuttering” Bug
Whenever you have more than 10 observations from a batch upload queued, selecting the taxon search tab always causes the opening tab to “jitter”/“stutter”/“stall”, it’s pretty disruptive and noticeable when it happens on every single observation. https://youtube.com/shorts/wJuK7hgZqRo?feature=share
Bug #3: Poor or Failing WIFI Connection Resulting in “Blank Images”
Regardless if you selected the photos offline or with an internet connection, or if you selected them minutes to an hour prior, if your WIFI connection cuts out in the middle of a batch upload, it causes images to go entirely blank/invisible, only appearing again when the connection is reistablished. https://youtube.com/shorts/tTVdLC2rUCs?feature=share
“Bug” #4: Abysmally Slow Uploading Speed
Even with only 68 observations queued, this video is 5 minutes long and shows the new app failing to successfully upload two observations (one of which was already well into being uploaded when I thought of starting the screen recording), with the extremely slow uploading speed resulting in both of the started observations failing/aborting as uploads and being skipped in the queue. https://youtu.be/MNDjrEqyp1o
I can’t speak to all of the glitches you describe, but queueing up “only” 68 observation on the mobile app for upload is probably taxing the system (your Bug #4). I agree that this limitation is frustrating, but I usually keep my upload batches to no more than 10 to 20 at a time when using the mobile app (1.0.19 (206)). Even then it can sometimes take 30 to 60 seconds per observation upload to complete each, depending on the strength of my internet connection. Wi-Fi obviously helps upload speeds, so I limit my uploads to batches of 2 to 5 at a time when I’m in the field without a strong cell signal. If I’m down to one or two bars (even with 5G), I don’t even try to do uploads in the field.
The app just plain and simply doesn’t work. I open it, I get to click maybe one thing, and then the entire thing becomes nonresponsive to touch inputs.
I haven’t ever had this problem with iNaturalist Classic which is why it feels worth mentioning, compared to my usual uploading volume 68 observations truly is very little. My standard observation count for a usual day is situated between 100 and 700. I normally queue my entire backlog at once on iNaturalist classic and it uploads without a hitch, so I’m confused and a bit surprised why it seems the new app can’t handle a fraction of it.
All three of these batches uploaded flawlessly and quickly - finishing in about an hour or two without a single issue. Even with shoddy WIFI connection.
I’m OK with these being under one report at the moment.
I agree with @gcwarbler that these are a lot of observations to be importing in one batch. I try to keep it to 10-20 or so at a time. The app supports the import of hundreds of photos, so I think it shouldn’t be failing like this, but I suspect very few people are importing this many observation at once.
I agree the app has some upload issues, but I’ll also note that in the video you only have two bars of Wifi, which to me signals the connection isn’t that strong and may be going in and out.
It looks like you’re making hundreds of observations of one species, like each individual alfalfa in one day? Frankly, iNat is not designed for recording abundance like this. May I ask what your goal is by doing this? I’d recommend just making far fewer observations, maybe a representative or two of the species of interest.
Unfortunately this isn’t feasible with my observation output
The alfalfa spree is a one-time instance to prove their abundance with solid data by going on a 2 hour walk and taking photos of every individual I see - without veering this thread off topic, Alfalfa is an incredibly destructive species that the province and most invasive species trackers refuse to acknowledge or label as invasive (likely because of their tie in to agricultural profits)
This isn’t my normal observing process, nor do I intend to do it again in the future, I’m not sure how it’s relevant when it doesn’t make up even 1/55 of my account and isn’t related to the bug report.
I’m currently homeless and only have access to public WIFI networks, I will reiterate that even with a shabby connection iNaturalist Classic hasn’t had any issues with extremely slow uploading times like I’ve experienced with iNaturalist Next in the video above.
the team should take this into serious consideration IMO, especially since iNat observations are severely underrepresented in impoverished regions. I’m of the personal opinion that any app or game etc should have a setting/option that allows it to run on the computing+connectivity equivalent of a lemon battery and baked potato
I haven’t used iNat Next since it first came out because of these issues, but decided to give it a try again.
I’m not sure I understand the comment pointing out the alfalfa observations, because it doesn’t help address anything about the app issues. And, a 10-20 observation upload “limit” also does not work with my observing process (1 or 2 representative individuals per species or form…).
I have very good connection from my house. I use a pretty new phone that runs other things quickly and smoothly. The old iNat app and website work fine and upload fine.
I decided to upload just 39 observations from the app, which is just a small portion of what I took today.
I experienced Bug #1 a lot. It was very annoying.
Bug #2 also happened, but was more of a nuisance than being disruptive.
I can’t speak on Bug #3 because I have good and stable connection.
“Bug” #4 is absolutely horrible. I clicked “upload” at 16:39 and it finished only at 16:53, with 2 failed observations. With this time, I could have transferred all my images from today (hundreds) onto google drive, downloaded them on my computer, and uploaded them on the website. I really do hope this speed is fixed, because I’m not sure I can work with 39 observations taking 14 minutes to upload… :(
For further context about upload speed (“Bug #4”):
(I know the iNat website is on my computer. But, at least my phone and computer share the same network…)
iNat Next uploaded 82 images for 39 observations, using 14 minutes
iNat website uploaded 209 images for 106 observations, using 4 minutes
Fair enough, I agree it wasn’t directly related to the bug and I’ve removed the link.
@zee_z Are all 4 bugs from the same session? They appear to be but I want to make sure. What I think you’re doing is importing photos, and you made 69 observations out of them in the Group Photos page. Then you tapped on the green “Import 69 observations” button and are going through them one by one and adding IDs. And then you’re tapping on “Save”, correct? (I wish iPhone screen recordings recorded taps) I’m not seeing any upload progress bar so I assume you are.
And then, after they have been saved, you’re trying to upload them as a batch?
Yep! All 4 are from the same session, and that was my process exactly. Batch select photos, merge/group what I needed, go through and identify them while they’re unsaved, and then save them as a batch and upload them together as a batch. I’ve attempted to individually save or upload them from a batch before but it still took a significant amount of time (I can grab screen recordings of that if it’s necessary.)
Using our latest beta version I imported around 60 photos yesterday, and grouped a few of them so that I had something like 58 observations. Going through and adding IDs and saving them went fine, I didn’t notice Bug 1. They also uploaded fine and at what I think is a decent speed, about 5.5 minutes for 57 obs (I accidentally chose to upload one after I IDed it instead of saving).
Major caveats being that I’m on very fast wifi and most observations only had one photo.
If you want to try the latest beta, you join the testing program here: https://testflight.apple.com/join/bkGNs3ke There have been some fixes with the goal of making the app faster and more stable.
