rfresh Well-Known Member Licensed User Longtime User Mar 30, 2012 #1 When using the Log() feature, after we are done developing our app, should we rem out those Log() statements before deploying the app to the public? Or are they ok to leave in?
When using the Log() feature, after we are done developing our app, should we rem out those Log() statements before deploying the app to the public? Or are they ok to leave in?
Erel B4X founder Staff member Licensed User Longtime User Apr 1, 2012 #2 If you check the unfiltered logs you will see that many applications post many messages to the log system. You should however make sure not to post any sensitive information as other applications can read the logs. Upvote 0
If you check the unfiltered logs you will see that many applications post many messages to the log system. You should however make sure not to post any sensitive information as other applications can read the logs.
H Hubert Brandel Active Member Licensed User Longtime User Jul 21, 2014 #3 I see that the app is runnig slower with LOG shown in the IDE (even without debugging). I know that all this printing in the IDE tooks time, but does LOG() without a connected IDE slow down the execution ? I do load here 1000 lines CSV files with LOG() the keys to debug it. Upvote 0
I see that the app is runnig slower with LOG shown in the IDE (even without debugging). I know that all this printing in the IDE tooks time, but does LOG() without a connected IDE slow down the execution ? I do load here 1000 lines CSV files with LOG() the keys to debug it.
eps Expert Licensed User Longtime User Jul 21, 2014 #4 Maybe remove or REM excessive logging.. You need to make the call yourself. Just to be clear - the App isn't generated in debug as well is it? Upvote 0
Maybe remove or REM excessive logging.. You need to make the call yourself. Just to be clear - the App isn't generated in debug as well is it?
H Hubert Brandel Active Member Licensed User Longtime User Jul 21, 2014 #5 No I have compiled it with "Release" and it starts without debugger, but it shows the LOG output. After thinking about it, IF other apps can read the log, it is stored and I have to remove it. Upvote 0
No I have compiled it with "Release" and it starts without debugger, but it shows the LOG output. After thinking about it, IF other apps can read the log, it is stored and I have to remove it.
Erel B4X founder Staff member Licensed User Longtime User Jul 21, 2014 #7 Not exactly. Starting from Android 4.1 other apps cannot read your app logs. The logs are only visible through ADB (usb debugging). Upvote 0
Not exactly. Starting from Android 4.1 other apps cannot read your app logs. The logs are only visible through ADB (usb debugging).
eps Expert Licensed User Longtime User Jul 21, 2014 #8 Erel said: Not exactly. Starting from Android 4.1 other apps cannot read your app logs. The logs are only visible through ADB (usb debugging). Click to expand... Erel, is this also the case for rooted devices? Upvote 0
Erel said: Not exactly. Starting from Android 4.1 other apps cannot read your app logs. The logs are only visible through ADB (usb debugging). Click to expand... Erel, is this also the case for rooted devices?
