Characters like 直 and 写  get rendered using Chinese font on Android. I have Japanese set as a system language and a japanese key board installed. To resolve all text in app should be explicitly tagged as japanese to prevent defaulting to Chinese encoding.

Is there a way to detect this?  If so, can it be fixed in-app, or do I need to display a warning (and ask them to fix it themselves)?  Are there other default system fonts this applies to?

1. Start the app fresh for the first time 2. Connect to Wanikani API 3. Claim you can write all kanji that you have caught up in Wanikani. Expected outcome: Able to do something on study screen Actual outcome: Can't do anything, says "come back when there are more reviews".  Not a good first experience.

We should allow them to "review ahead" or something

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

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

Repro steps:

1. Launch app with Wanikani API enabled

2. Click 'Start' while API is still loading

On rare occasions this causes a crash

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."

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

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! 

The stroke order of 潟 appears to be incorrect.

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

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!

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?

Audio for first word of kanji 輿 is かご but should be こし

In the base kanji 木 the middle vertical stroke is quite strict. This also occurs when it is a component. If the stroke is done fast it sometimes registers it as not crossing into the second quadrant and marks it wrong. 

For 否 in the example for no it shows the hirigana ひ instead of いいえ. However it is still pronounced in the audio as  いいえ.  

See https://ibb.co/M89QHqy