iOS queue order settings for vocab seem to be broken. I can’t change the sort method or set a review limit (or at least the settings won’t persist).
Edit: Actually the SRS strictness in the “full settings” area also still doesn’t work. I don’t think that’s ever saved properly for me since I started using Bunpro (it’s stuck on -1). Very frustrating because it means I’m constantly manually adjusting SRS levels mid-review.
Still looking into this.
Basically what happens is that after adding a single new item to a Deck, it manually goes over the entire Deck and reorders it.
This means that the smaller the Deck, the faster it can add new items.
That’s why the Deck addition process stalls out at about 3000 items – reordering makes the network request time out.
Gonna work on fixing this now.
Please don’t touch your Samurai Champloo Deck until I’ve finished 🙇♂️
EDIT: @haldo I’m made fixes and performance improvements to the Import tool.
It can now better handle larger (3000 Vocab+) imports at once.
I’ve added the all the words from that CSV file to the Deck.
I created a new account and as a beginner I wanted to start with hiragana and katakana but the content is in Spanish and there is no settings available to change the language to English unless I skip the complete introduction.
Some of my ‘on the hour’ reviews are no longer releasing on the hour.
I have always had my reviews set to ‘on the hour’ but over the last few days I have noticed that sometimes when hitting the next hour and the reviews move over, they don’t actually ‘release’ into my review pile, and it stays in the forecast for the current hour. Trying to keep and eye on it and it looks to release right at the end of the hours, like 50-55 minutes past or something. It doesn’t seem to happen very often from what I have observed.
Yeah we’re aware of this and an update should be coming ASAP for it, sorry!
In the meantime, if you want to continue learning on your phone you are still able to do the kana learning in English if you visit bunpro.jp in your browser
Sorry again for the inconvenience!
Yes, it works in the browser. Thank you for the update.
The blur suddenly makes stuff disappear. It happened with multiple items. Tapping on the space made the sentences visible again. Mobile, ipad, browser is safari.
I’m not sure if the Bug Reports thread is the right place to report this, but it looks like some of the links to external sources for the について grammar point aren’t valid (anymore). The Imabi link simply directs to their “about” page, and the Nihongo Shark link comes up with a “page not found” message.
[Edit] By the way, there’s something I was wondering about, concerning that same page. I’m not sure if it’s a mistake or simply something I’m overlooking, and if it is the latter, I apologise! The explanation about について mentions that it’s a combination of に, 就く and て, and at the bottom of the page it is explained that the kanji 就 is rarely used in this phrase. But at the top of the page, the listed “rare kanji” is 付, not 就. Is that right?
Self-study vocab reviews are becoming a pain so I’m trying to remove them from my reviews. Unfortunately I can’t seem to do that either on the website or on iOS. Anyone else had this issue?
I’ve tried removing any self-study sentences but still have had no luck.
Edit: Self-study sentences might be bugged. I just noticed that on words where I’ve deleted self-study sentences, when I refresh the page the sentence is still there. Seems like I’m unable to delete sentences, though it could be because there are Ghosts or something.
This is way too difficult 
(Iphone app, this is the only vocab it happened with throughout the review)
E: just realized this is imported from wanikani and simply not written in kanji to begin with
I noticed that the vocab word 尉 (JLPT N2) | Bunpro is marked at N2 but is in the N3 vocab list? But because it’s marked as N2, it’s not getting picked up by my daily N3 vocab words.
I know I can just add it to reviews manually, but I do find it odd that it is marked as both N2 and N3.
Hi there. Sorry for this annoying bug. 
We’ve had a few reports RE this. Including from @OtakuSupreme.
Two quick questions:
Looks like you managed to delete them?
I can see you’ve got no Self-Study Reviews anymore.
As for the sentences still showing, where are these sentences still showing? Mobile or web, or both?
Can you give me an example Grammar/Vocab point?
Might have been a temporary data caching issue with web or mobile.
Thanks for the response.
No daylight saving where I am, and I have had the time zone set to my city for a long time.
Just to make it more confusing: I have further noticed that there may be some reviews that release on the hour, but some don’t. E.g. If there is 10 reviews coming up at 12pm, 7 of them might release as it hits 12:00 and go into my ‘review’ pile, but 3 will stay in the review forecast for 12:00 until about 12:52 and then release into my review pile.
Yeah, there must be a delay somewhere that holds up the process, because I noticed them slowly disappearing after a while. Sentences now seem to be gone but I’m still seeing some ghost reviews.
Reluctant to file this as a bug because I feel like I might just be missing some other way to read this. But just in case
the furigana on the summary says にち above 2日
shouldn’t it read ふつか?
Found the cause of this will have it patched with the next release. It was caused by vacation mode not rounding the review when it was bumped.
Hellooo!
I add a lot of self study sentences, and I’ve noticed that when I’m typing into the fields using the Japanese keyboard setting on my MacBook (using Safari), every time I type a letter, it also puts out a duplicate of whatever I have typed up to that point. For example, if I type on my keyboard: aiueo, it comes out like
あいうえおあいうえあいうあいあ
instead of just
あいうえお.
This doesn’t happen when I’m using the normal English keyboard, and it also doesn’t happen when I’m in a study session answering typed questions. I also sometimes add sentences using my work laptop (Chromebook), and this doesn’t seem to be happen at all on there either.
I would appreciate it if anyone could help me figure out what’s going on here.
We corrected this yesterday! If you find any more you think are incorrect, feel free to send them over via the bug reporting feature. That way we can keep track of what has been corrected vs what is still open and can give you verification the issue has been solved!
Apologies, I hadn’t realized there’s a button on the page for that, will do!
