Frédéric Julian

That is a v1 screenshot. From what I know the v2 should display it in a better way, could you confirm that?

On my side I would definitively accept such a feature (at least if the code is nice enough)

Well, no it's not. Sorry, but when I published the v2 I closed every existing issues. There was a lot of obsoletes and a lot of advertisement posts at that...

doing a iOS app would means rewrite everything from scratch, and that is not planned at all (even if I would love to see a Flutter rewrite of this app,...

I can confirm Google and Apple don't like apps with donation links (I got an app rejected last year due to that). Also, for your information I got some difficulties...

It's a complicated and quite massive dataset, so I wouldn't be surprised at all that one of the data is above 4kb, even if I can't easily check that. But...

I managed to reproduce the crash on windows with a data above 4kb. Here is an example app: [testisar.zip](https://github.com/isar/isar/files/9762950/testisar.zip) You need to press the button at least 2 times to...

After some investigations, it seems that the culprit is the ObjectAnimator with setRepeatCount(ValueAnimator.INFINITE); Without this line I have no memory leak.

This actually seems to be a jack bug: https://code.google.com/p/android/issues/detail?id=213471 See another related discussion here: https://code.google.com/p/android/issues/detail?id=214615 It is marked as "FutureRelease", which means with a bit of luck it will be...