While I understand it may not be commonly used anymore, some of us are required to learn it for class. It would be super helpful for those of us that do, if this katakana could be added to the custom lessons.

I have a phone with square screen. The initial screen with the tomato, and the study screen for reviews don't show completely. The study screen clearly cuts in half the 'review only' button, but for the tomato screen I'm guessing what is hidden is a custom study button, but I couldn't find a screenshot to compare

After updating all my databases to the latest versions, some kanji were REMOVED from the JLPT lesson.  I need to figure out:

* What kanji specifically were removed? * Why were they removed? * If a user learned that kanji previously, does this cause any problems?

Hello,

I showed my kanji professor this app recently and we have discovered two issues:

1. There is a missing kanji in unit 25 between 特 and 低, which is 県.

2. The way of writing 冷 is outdated, it should be written like the way the kanji is typed, but just to be sure, I will add an image. Could this be changed?

Thank you very much for your hard work!

The stroke order of 潟 appears to be incorrect.

Stroke order reference: https://kaku-navi.com/kanji/kanji08544.html

I should probably make sure not to include more than 50-100 items per chapter.

1. eg. 連れる

Consistently happening in v0.22, when testing for 説

It wasn't the first kanji in session.

I started on a Galaxy S10E but need to start using and iPad Air 2 (Ver 15.5). After I select the file, type yes, then select "Import", it crashes.

I'm learning 心 but the app is asking me to draw something else.

I just picked up this app due to finding a post about it on reddit, looking for something to help me learn the stroke order of kana because I learn best by writing them. Immediately upon starting my first lesson, I got a pop up saying "Tutorial: Hiragana." However, the text was nearly unreadable. It was white on a white background. I thought it might be an issue with my brightness settings etc. and discovered that after turning off dark mode, the text became black and I could read it. This is a temporary fix but I'd like to not

Hi! Thanks for Ringotan and for the recent update! I love it, and I recommend it a lot to fellow learners.

Somehow I got my Ringotan to not ever let me do reviews. It's showing "0 review (of 4 total)". But I don't get reviews, nor can I do reviews only.

I tried completing a lesson, and that didn't help either.

I can go to Custom Review and sort by Time to Next Review, and I do get things that are due Now. I can select them and review them, and the number of reviews goes down.

Any suggestions?

The Custom Review button is behind the home bar on iPhone. It needs that bit of extra margin that keeps the app from going to the bottom of the screen. (The name of it escapes me...I develop for iPhone sometimes but my brain is in Japanese mode.)

It's not that bad, because I just figured out that the whole bottom of the app is the Start Review button, but it can be a little confusing.

iPhone 15 Pro Max, iOS 17.2.1.

Thanks for Ringotan! 

Thanks for all your hard work on Ringotan. I appreciate the ongoing updates and support, and am really pleased with the WaniKani integration. I am running into an issue where the WaniKani integration status on the home screen and reviews screen displays this "String was not recognized as a valid DateTime" error string, and has done since the first time I hit the little refresh button there.

I haven't been able to get it to go away to try and replicate it, so I'm not entirely sure how to reproduce it, but it doesn't appear to impact the functioning of

Repro steps 1. Enable Wanikani API 2. Let it refresh 3. Complete a really long study session (> 60 minutes) 4. Go back to the main screen

Above error is shown

Repro steps: 1. Have Wanikani API setup 2. Reset data of entire app 3. During setup, choose "Enable Wanikani API Integration"

The API won't refresh as expected after setup is complete.

Workaround: Hit the 'refresh' icon

Today I increased review frequency from "normal" to "frequent." My kanji per lesson went from 18-22 max to 27.

I haven't touched the setting for "kanji per lesson."

Apparently the only crash that's happened in the current version (which is pretty good!), happening to <1% of users.

Stacktrace just says there's a null reference exception