Ok, thanks to @naramsim for identifying the issue only effected folks who tap the emoji hand (as opposed to mashing the enter/return key), I was able to quickly reproduce and fix the problem. I got a few emails over the course of the day with the issue, so I’m grateful you figured out how to reproduce it! 
You’re welcome! And thank you! For making this great free app!
Absolutely, this isn’t stated enough!
First time I got bit by my own shame-inducing review inbox icon LOL:
Are there any plans to be able to suppress or combine kanji lessons that are identical to a vocabulary lesson or vice versa? I don’t mind so much on Wanikani because there’s usually a different reading so it’s worthwhile, but it’s such a pain to enter a single kanji by on’yomi in the IME (and on top of that it contaminates suggestions) so I usually end up using kun’yomi or using a compound word and deleting one… being able to limit that process to only kanji that don’t have a single-kanji vocab word entry, without entirely disabling kanji learning, would be nice.
@discobot start advanced-tutorial
It’s been a while since I’ve demoed myself using KameSame, so here’s ~20m of me doing reviews, using the list placement test, and using the scan-content-for-lessons feature:
Please excuse my ugly handwriting
hey searls, just to know, do you have any intention of fix this? It’s really awful not be able to see kana 
Sadly, while I test KameSame in Safari, Firefox, Chrome, Edge, and Edge (Chromium) on macOS, iOS, and Windows on each platform those browsers appear, and I still have not been able to replicate the bug in which kana are not rendering, so I’m at a loss for how to fix it.
It exists, but it’s Chromium based, so there’s basically no difference between it, Edge, and Chrome besides the buttons themselves.
what does the weekly stars means? its just for self encouragement? sort of meta?
You earn a star for every 50 items you do a lesson for in a given week. Doing lessons is how you fill your review queue which is the primary way to expand your vocabulary in Japanese, so it serves the purpose of having some system to motivate people to do a baseline number of lessons each week.
With the latest layout, how do you now mark items burned in survey mode? When I get an item correct it auto advances to the next item… I can only get the page to pull up if I don’t use the kanji and get a “well it’s a valid reading” page.
I use survey mode as I don’t currently want to add lessons.
Yes, I noticed this and agree. I’m deploying a change now so that Survey lessons will ignore your “skip results page for correct answers” preference
Still love this ever-improving app! Quick question – for a while, you had handy-dandy anchor links at the top of the Lessons page (mobile version). This avoided me having to scroll past the two new items, when all I really want to do is check if there are any new “Study WaniKani items” available.
A number of days ago, those top-of-page anchor links disappeared. I wasn’t sure if that was on purpose, or if they fell out inadvertently during another update? (Or, if there’s a way for me to custom reorder things on the Lessons page, that would solve the problem even better – I just wish the WaniKani lessons were at the top. 
)
Thanks again for the wonderful app! It’s the only thing that’s ever moved me to jump onto Patreon.
Sorry about that. I only had added them as a stop gap because the previous list UI was 5 or 6 times taller than it is now, which meant an undue amount of scrolling. I’m actually going to make it a decent bit shorter still soon.
Longer term I need a strategy for organizing the growing types of lessons you can do. I don’t like the idea of a tab-view-within-a-tab-view but I don’t have a lot of great ideas just yet
Thanks for the info! Maybe allowing users to reorder the blocks on that page would work?
You may think of something better, and, of course, I realize this would be low-priority versus other changes. Whatever works!
Thanks for the reply! What a great app!
hey searls, me again. I’ve briefly searched in ur html and found that the attribute lang = “ja” causes the render bug. I’ve tried replacing it with “jp-ja” and take if off and both works. Idk if you gonna consider it since it could affect the other browsers, but for all the people that uses Opera would be ok if you change the lang of your browser to japanese.
Also, really thank you for developing this, it so fucking useful hahah, especially adding words from external sources. 