LOGCAT events not reliable
Answered
Starting from version 4.26.3 of MyLibV2 RC13_1149_beta and further, with each update, different events suddenly began to arrive in logcat when opening the dialog for adding a point to a recorded track.
For example, for version 4.27.0_1150_release
START u0 {cmp=menion.android.locus/o.lastKey (has extras)} from id 10102 on display 0
After upgrading to version 4.27.1_1153_release
START u0 {cmp=menion.android.locus/o.comparator (has extras)} from id 10102 on display 0
This has never happened before.
Now we have to fix profiles in tasker after each Locus update, which is very inconvenient. Is it possible to avoid such innovations?
Hello,
this was not happening before? I do not think so, sorry. If you relly on such notifications, there is no way for me to make them identical in every app version, sorry.
Names of classes are simplified and randomized with every app version.
Hello,
this was not happening before? I do not think so, sorry. If you relly on such notifications, there is no way for me to make them identical in every app version, sorry.
Names of classes are simplified and randomized with every app version.
Replies have been locked on this page!