@JuliusMigaku Hi Julius, sorry to ping you directly on a bug thread but I haven't seen an update here from Migaku's team in quite some time and from what I can tell this is affecting a non-trivial number of people. Scrolling through the replies and I also see a number of users who specifically stopped their subscription because of this issue. It's also a fair assumption that a number of people have stopped their subscription because of this without posting here.
I have also supported Migaku for almost two years now and as long-term customer I would really appreciate some insight into whether or not this is prioritized as an a issue. I understand replicating and this must be difficult, and thus fixing it must be even more of a challenge.
Lower in the thread I did recommend some work-around, or band-aid solutions that, while admittedly are suggested with complete naivety and no knowledge of the code base, if possible, could lower the severity of the issue by simply making it less noticeable.
Would appreciate some insight into this from Migaku's side of things if possible. Thanks so much in advance.