I think you’re the first person I’ve seen with that lv102 badge. Cool!
Though I think Jake is going to have to make 103, 104 and 105 badges for you within the next few weeks. 
I think you’re the first person I’ve seen with that lv102 badge. Cool!
Though I think Jake is going to have to make 103, 104 and 105 badges for you within the next few weeks. 
It’s fixed! Thanks for the help.
Nice! How about for rabbits at level 103? 
I’m not sure if this is a bug or intended behaviour, but I thought I’d mention it here just in case.
I just completed ten regular reviews as well as two wrap-up items from yesterday. In the activity graph on my dashboard, the wrap-up items are counted as reviews done today. Which I somewhat understand, but the actual reviews were done yesterday, that’s why I was wondering if this behaviour is intended or not.
102レベルの同士!
I’m not sure if it fits the topic, but I’ve got confused by the contradiction in the definition of さようなら and examples of it.
So it says “not expecting to see the person any time soon”, but at the same time there is “see you tomorrow” example. Aren’t these mutually exclusive?
3rd example is a possible “missing definition”. Younger age students / daycare kids and their teachers use this as a goodbye, even though it’s almost certainly a temporary parting.
Children use it a lot too (more generally speaking). See this example from Usagi Drop:

Shop Keep:またね りんちゃん。
Rin (The child): さようならー!
Hi, I also experience this on Android today.
It plays neither automatically nor when I click the play button.
I’ll see what logcat has to say when I have a chance.
version 0.5.2
bunpro.jp.bunpro_srs
Android 16 on Pixel 7a
By the way, when I tried to log in here the first time I got “Internal error” and then was kicked to the dashboard 
I found an on-device log reader.
After submitting correct, it logs an audio URL, but nothing about any attempt to play. (first screenshot)
When I tap play I just the same four entries appear each time; they don’t seem to have to do with playback. (second screenshot)
Incidentally I maybe found bad usage of a logging function; it mentions stack trace so maybe it is actually trying to log something after all?
(third screenshot)
Sigh, I guess Google did its staggered update thing; I just received 0.5.4 today (which says released 15 Mar 😮💨). Anyway, I see “Fixed audio playback problems for android” in the changes, but unfortunately problem continues in this version.
I’ve fixed this as of next update!
Thanks for the report 🙇♂️
expected behaviour: searching for the katakana form, should yield the result, since it’s listed as one of the forms.
In these instances, we can change the metadata so that they do show up in searches!
I’ve just changed this for クソガキ!
Might take a look at automating it using the JMDict data too actually.
Not the intended behaviour, and as far as I can tell, not how it should be working.
It should be assigning the time based on the final submitted answer.
Will keep my eye out for anything else related to this!
I always assumed JMDict was actually the source of Bunpro’s vocab data since very often, the definitions are really 1:1. So I thought this was a technical / broader issue. Otherwise I would’ve just reported it on the vocab item. But thanks for looking into it!!
Not bad for my very first N3 practice test, that’s a true girigiri 
However it seems that the pause feature still needs improving : I did 1-2 questions of listening before pausing, quitting the page entirely, and then came back to it ~1 week later. The display timer earlier did tell me that I only used up around 3min, however after going through all of the test and getting my results it went from “you used 27min” to “you used SEVENTEEN HOURS” 
(no before-results screenshots, I wasn’t aware I was gonna need one so I didn’t take any)
When completing a review session, it now always says that no reviews were done during the session, though it does correct itself after a few seconds 
I just had the same happen to me. The “no reviews” message was there for a split second, then the actual results appeared.
Can’t say I’m particularly bothered, but I figured it might be helpful to make clear that the issue isn’t unique to the pro bunny.