Actually, just now it took a good seven or eight seconds for the results to appear. Meaning the message “no reviews done” was on my screen for that long. Yesterday it took only a fraction of a second, that’s why it didn’t bother me. But seven or eight seconds is a bit too long.
1 Like
since about two days I sometimes get the same error, too - except that unlike the other people who reported it, mine doesn’t load the actual results after a few seconds. However, I’m one of those very rare Firefox users which might explain the difference in behaviour
According to the dev tools, the culprit seems to be this XHR call:
https://api.bunpro.jp/api/frontend/summary/last_session?review_session_id=[reviewid]
which takes a lot of time and the empty page renders before the response arrives.
In the case of this small review (5 questions) the response took 600 ms to arrive and did render the page. My previous review was ca. 50 questions, and there it didn’t render. I assume it took substantially longer with the more questions, and some other event fired in between which led to it no longer rendering based on the response.
1 Like
I was also on Firefox. 
1 Like
Chiming in as another data point for the delayed reviews summary - I’ve also noticed that the “last 24hr” section doesn’t seem to update, even if the summary for an individual section does eventually show up.
1 Like
Recently we made an update to make cram use the summary page
seems like that made some problems with the page’s loading state. 
Just updated the page to show the loading state correctly
will keep an eye on the thread if the problems still persist 
4 Likes
Don’t know if this is necessarily a bug or not, but see when doing the JLPT Practice Tests, if you exit out of it, does the timer not stop?
I did an N4 grammar test yesterday. I did a portion of it during my lunch break in work, and a portion of it on the train home after a social thing and it said it took me 13 hours. The timer during the test itself seems accurate enough, it’s the one on the results window.
2 Likes
at least for me it still persists but just in case, I now deleted all relevant caches. I might simply still have had an old version of the frontend.
1 Like
Unlreated, found another one. This one is cool!!
The expected behaviour is that If you set a goal size 0, you can set the batch size larger than the goal size, but if the goal size is >0, you can only set the batch size to be at most the same as the goal size. So far so good, that’s expected behaviour and works perfectly fine on desktop.
on mobile however, if your daily goal is zero, you can only set a batch size of zero or 1.
so:
- Bug 1: the batch size can be zero on mobile if the daily goal is zero (I really wanted to save it as zero and start a learn batch to see what happens but I don’t dare risk corrupting my account
) - Bug 2: the batch size on mobile can not be set freely but is capped to 1 if the daily goal is zero
2 Likes
I just did a very small review session with only 6 reviews. I got the last review wrong, the other questions right. With the 6th review still on my screen, I clicked the “exit” icon, expecting to be asked if I wanted to wrap up, but instead Bunpro moved on to the results screen right away.
When I started another review session afterwards, the review that I got wrong earlier got tacked onto the new review session as a wrap-up item.
2 Likes
Now I’m seeing “おっと!” after every review session, but more of a loading screen instead of the previous “no reviews were done” type of screen.
It’s a step forwards from where we were, but it’s still a bit dispiriting to see every time 
2 Likes
@thelizard
Thanks for the report, I got it fixed and the patch will be released with the next update
2 Likes
1 Like
Comming with “really important and urgent bug that I am sure will be tough to fix”.
As you can see on atached image there is empty box in the first caution segment of an い ending senence particle. As it is archaic and marked as JLPT N0 I am sure many students have to struggle with that every day.
3 Likes
I just reviewed 40+ words/grammar points, and when I finished it said I had gotten 0% correct. This is the second time this has happened.
What happened to the answers I gave? Did it register my answers correctly and is just displaying the incorrect percentage, or has my progress somehow been lost?
1 Like
In the past I lost my streak because I was pretty sure that I didn’t do any lessons/reviews on a certain day, but today when I logged it shows that I did not do any lesson yesterday which is not true, because I was doing reviews on the mobile app, and now I started to think if the previous lost streaks happened because of the app too? The app was working as usual, I got the notification that I finished the session and so on, so I am not sure what’s the problem, and how to make sure that my streak is preserved 
I guess I will have to check each time if it is actually preserved on the main screen, but just wanted to let you know!
1 Like
During my reviews, I got the same sentence twice.
- It was a ghost
- It wasn’t wrap-up from a prev. session, afaik
- All the questions were grammar, no vocab
- During the middle of the review, the top green bar went back-and-forth a bit (from about 25% to 20%, then back), as if it couldn’t decide if the session has 4 or 5 total items.
- The second time the sentence appeared, it was the last of the session, and the green bar filled to 100% (afaik this shouldn’t happen)
- The summary page also shows the sentence twice, see screenshot
wasEmpty=false&wasForceQuit=false&isPostQuiz=true&reviewSessionId=23256531
EDIT: I also have a browser console log, that has some interesting info (e.g. a “remainingCount: -1”). I can’t attach it here, so if you need it, please tell me, who to DM/email.
2 Likes
I’m still having issues with the “In the last 24 hr” review accuracy not updating.
Edit: A picture, in case it helps.
The percentage, actual numbers, and list of missed answers are all from multiple sessions ago (from sometime yesterday, I believe). The “This session” tab loads correctly, though.
1 Like
Fixed! Thanks for the heads up.
I have removed the empty space!
Thanks for the heads up 🙇♂️
2 Likes
I believe this may have just been an incorrect loading state.
Have you noticed it since? We pushed an update to fix it roughly a day after your message.
Apologies for the inconvenience!