After going through N5 and N4 vocab I can certainly find my way around a Japanese hospital:
眼科
歯科
外科
内科
耳鼻科
皮膚科
産婦人科
整形外科
edit: and don’t forget to take your 抗生物質
3 Likes
That’s not actually a bug. From what I understand, they put all vocabulary from Genki I into the N5 deck and Genki II into the N4 deck, which sometimes results in oddities like that.
1 Like
I forgot to mention that this has been resolved.
Thanks for the hard work! 
1 Like
Hi there!
Sorry for the late reply, and thanks for following up.
Are you able to please:
- Tell me what versions you are running
- Then update your version of MacOS/iOS and also Safari and tell me if this fixes it?
I couldn’t replicate this issue, but other users have fixed it by updating their versions.
Thanks,
Sean
Fixed!
Thanks for the feedback 
1 Like
Hi there! Welcome to the forums 
Very surprised no one has mentioned this until now…
I’ve now fixed this. Thank you!
1 Like
Thanks. As I wrote above the phone is running iOS 15.8.2. That’s the current release on the iOS 15 branch. It’s too old to run iOS 16 or 17 so I can’t update it any more than it’s already updated. Safari on the iphone updates in tandem with iOS so there is no separate Safari version. For what it’s worth though the site works fine in Safari on my laptop and it doesn’t work on Firefox on the phone so it’s very unlikely to be a Safari problem. I’ve been using it on the laptop the last two weeks but I’d really prefer to be able to use it on the phone again. I understand if you’re unable to fix it or are unwilling to spend the time if I’m the only one affected but in that case please let me know so I can cancel my subscription.
1 Like
What version is the Macbook you’re using?
I’ve heard of people having problems with v15 of iOS/iPadOS.
BTS iOS uses the same engine to run all 3 browsers, so yeah very much a MacOS/iOS issue.
All the other users have had this problem were on v15.
I’ll try emulate this and see what I can do.
Hello,
I just signed up this morning and went over a couple of grammar points just fine.
Now trying to access my dashboard automatically redirects me to onboarding. Finalizing the onboarding and clicking Study now! results in a continuous onboarding loop.
Thank you for looking into this!
3 Likes
Same situation for me, so not an isolated incident.
2 Likes
Same here, tried different browsers (Firefox and Edge on Fedora). This should be pretty easy to spot.
2 Likes
This should now be fixed.
Welcome to the community everyone, and I apologize for the negative first experience with Bunpro!
5 Likes
The phone, where things don’t work, is an early iPhoneSE. The macbook, where things do work, is an M2 Macbook Air.
1 Like
This uses the wrong “rare kanji” for をもって, it uses the ones fore まして.
Since vocab was added to cram, I haven’t been able to cram after a review session. It works just fine from the main cram page, but I can’t do it after the reviews.
1 Like
Hey, don’t know if this is a bug or not but on the app (ios) i had it ask me the same question multiple times. Like i had to answer でしょう and だろう three times each. I think it may of happened because i had to do it offline as i was travelling and didn’t want to use my data.
1 Like
I can’t seem to turn off vacation mode. It’s been slow in the past, requiring me to close and re-open the app multiple times for it to finally work, but it’s been about 5 minutes now and vacation mode just won’t turn off, so I can’t do anything. the little off switch finishes loading in the menu, but when I go to the home page it’s still in vacation mode.
I noticed yesterday my desktop page and mobile app were also not syncing properly. My mobile app was showing that I had reviews to do, even though I had finished all possible revies on desktop.
1 Like
Also i think it’s given me waayy too many reviews. I haven’t added any new items today but i have 35 reviews on top of the 50 something I already did. I only have like 35 n5 grammar points. I think maybe it’s overwritten my offline reviews with the online reviews (that i haven’t done) maybe?
2 Likes
Hi there!
This indeed appears to be a big 'ol bug.
We’re looking into it.
2 Likes
I believe Jake found the cause of this issue.
Fix will be published in a few days.
2 Likes