Provost Simon

> Thanks for the PR. I will have a closer look later, but just had a superficial glance now. I can not give you a timeline on the review, unfortunately....

_Sorry for the lengthy response ! I tried to be as thorough as possible in order to avoid being vague or confused! I do not believe that proper answers to...

> Hi Simon, > > I started reviewing the code. There are several suggested changes to simplify the code and make it more readable. I haven't dug into the changes...

> Finished my first look, and my first impression is very positive :) while there are definitely some things that I'd like to see changed to improve readability and maintainability,...

BRIEF UDPATE: I intend to start working back on all this from the end of this month onwards. I have an important deadline for the 20th and had no time...

@leightonvg Any advancements in this direction?

> Seems fine, though I would probably write it slightly differently. I do think it makes sense to have a global way to easily check what individuals have already been...

BRIEF UDPATE: I intend to start working back on all this from the end of this month onwards. I have an important deadline for the 20th and had no time...

BRIEF UDPATE: I intend to start working back on all this from the end of this month onwards. I have an important deadline for the 20th and had no time...

Could you write debuggable true even in release mode to see if it is your build variant that causes the problem ? Could you check it with another devices Android...