Various hooks spam logcat with "Lua Member is not valid"
essinghigh opened this issue · 5 comments
Seeing a spam of errors in logcat when applying options in XPL-EX
This also causes a lot of lag in the application - DevCheck is what I've been using to test this.
Couldn't find any mention of this in Github Issues or via Telegram.
XPL-EX Version: 1.4.2.4 beta
I do not have the Pro app or original XPrivacy-Lua app installed
Spoof Language gives the following:
05-07 13:19:22.171 12070 12314 W XLua.XLua$5: Message=Lua Member is Not Valid [toLanguageTag] Most likely not a after or before : now a:before
05-07 13:19:22.197 12070 12122 W XLua.XLua$5: Message=Lua Member is Not Valid [toString] Most likely not a after or before : now a:before
05-07 13:19:22.207 12070 12070 W XLua.XLua$5: Message=Lua Member is Not Valid [getCountry] Most likely not a after or before : now a:before
05-07 13:19:22.207 12070 12070 W XLua.XLua$5: Message=Lua Member is Not Valid [toLanguageTag] Most likely not a after or before : now a:before
Get Applications, Get Messages, Get Battery:
05-07 13:20:09.570 12761 12833 W XLua.XLua$5: Message=Lua Member is Not Valid [createFromParcel] Most likely not a after or before : now a:before
Get Sensors:
05-07 13:24:30.290 15879 15879 W XLua.XLua$5: Message=Lua Member is Not Valid [getSensorList] Most likely not a after or before : now a:before
Get Apps:
05-07 13:24:52.071 16058 16115 W XLua.XLua$5: Message=Lua Member is Not Valid [getText] Most likely not a after or before : now a:before
05-07 13:24:52.084 16058 16115 W XLua.XLua$5: Message=Lua Member is Not Valid [getPackageInfo] Most likely not a after or before : now a:before
ID Bluetooth:
05-07 13:26:06.499 16275 16321 W XLua.XLua$5: Message=Lua Member is Not Valid [isEnabled] Most likely not a after or before : now a:before
05-07 13:26:06.503 16275 16321 W XLua.XLua$5: Message=Lua Member is Not Valid [getState] Most likely not a after or before : now a:before
05-07 13:26:06.504 16275 16321 W XLua.XLua$5: Message=Lua Member is Not Valid [getState] Most likely not a after or before : now a:before
05-07 13:26:06.611 16275 16325 W XLua.XLua$5: Message=Lua Member is Not Valid [createFromParcel] Most likely not a after or before : now a:before
ID Build:
05-07 13:26:57.848 16575 16623 W XLua.XLua$5: Message=Lua Member is Not Valid [getRadioVersion] Most likely not a after or before : now a:before
ID Devices:
05-07 13:27:24.419 16758 16805 W XLua.XLua$5: Message=Lua Member is Not Valid [access] Most likely not a after or before : now a:before
05-07 13:27:24.420 16758 16805 W XLua.XLua$5: Message=Lua Member is Not Valid [exists] Most likely not a after or before : now a:after
05-07 13:27:24.420 16758 16805 W XLua.XLua$5: Message=Lua Member is Not Valid [open] Most likely not a after or before : now a:after
ID Network:
05-07 13:28:19.177 17328 17412 W XLua.XLua$5: Message=Lua Member is Not Valid [toString] Most likely not a after or before : now a:before
05-07 13:28:19.178 17328 17412 W XLua.XLua$5: Message=Lua Member is Not Valid [getHostAddress] Most likely not a after or before : now a:before
It's a lot to go through, as the majority of options cause this spam and lag the application.
Is this to be expected? I'm on a Pixel 7 Pro running LineageOS 21. Perhaps there is something I missed during setup.
Yes indeed it is spam , newer versions I will clean up logs and add more SDK MIN MAX Requirements, ill add it to the provided apis but that happens when the provided API is not available that's all , nothing you need to worry about but obviously it is spam to the log cat my apologies.
All good, no worries. Thanks for your continued work on XPL!
Will close this out as it is nothing of concern.
Perhaps the app just needs a verbosity level setting to help devs/users debug issues when set to high, but be set to low/off by default.
Even without the debug output, far too many messages are written to the logcat, which make the app unnecessarily slow.
Even without the debug output, far too many messages are written to the logcat, which make the app unnecessarily slow.
Slowly each update I will be cleaning up logs minimizing them, promise !