Doesn't happen on iOS, didn't happen prior to 0.20 update to iOS.  wtf!?

See images on phone, too lazy to figure out how to upload

Sometimes lines aren't captured even if you have drawn them for sure.

E.g. since I just started using Ringoton one of the new characters is 才.

The third stroke is never being accepted, the thin black line only goes from the bottom left to about 1/5 of the total length of the stroke. I've tried this about five times, always with the same result.

I've had occasional problems with detection of the drawn line on other characters too, but not like this.

Am I going crazy? These definitely used to be there, right?

Only like 5-10% of it is cutoff, it's hard to notice

With three いいい. Is that really correct??

Sometimes it looks like I should be starting close enough to the first stoke, but it fails anyways. I think this is only an issue on iPhone. Probably something to do with screwing up the pixel density calculation.

The app crashes when selecting custom Kanji to study on the new Android release. This does not happen for Hiragana or Katakana.

android adb logs is telling me some audio files are missing

java.io.FileNotFoundException: Audio/text-to-speech/kanji/N566RZEK.mp3

It still shows the default Xamarin icon. Discovered on release version.

See backup on phone.  Even though it's next on my list (and preventing me from "completing" level 14), it's not being added as the next kanji to study.

Button is out of place. Can test locally by commenting out the goofy broken file import code. Discovered on release version.