Hi,
When I build an APK in the code there is all print. Print are not use on device. It’s use less. And it’s can occure error when in the print there is concatenation or nil value. Why not remove those line during the build?
In my app I have a lot of print and when I remove all print before build the performance are increase.
Rémi
First, prints in your apk are useful. You can plugin your device into your USB port and use “adb logcat”, “monitor”, or Android Studio and view the messages on the device. Some things can only be tested on a device and this is a good way to debug your code.
Next, depending on the version of Corona SDK you’re running, you can re-assign the print statement to do something differently. We had some daily builds that blocked this feature but we’ve backed it out for now until we can figure out how to support it better. But for now you can do:
local debugMode = true local originalPrint = print print = function( ... ) if debugMode then originalPrint( unpack( arg ) ) end end
Please do not use the variable “debug”, it’s an important global variable.
It’s better to make the new print function local took but then you have to define it in all modules.
Rob
Then before you deploy a production build you can set your value of debugMode to false and it will stop your prints from showing in the console log.
I haven’t try but i think it didn’t remove bug when we concate inside the print(value…value) and a value is boolean or nil.
Trying to concatenate a nil to a string is an error in your code that would need to be fixed. The solution is to either test the values outside of the print and only concatenate them if they are not nil then print the result or don’t concatenate them, but use a comma separator.
Either:
local valueToPrint = "" if value1 ~= nil then valueToPrint = valueToPrint .. value1 end if value2 ~= nil then valueToPrint = valueToPrint .. value2 end print( valueToPrint )
or
print( value1, value2 )Thank you
First, prints in your apk are useful. You can plugin your device into your USB port and use “adb logcat”, “monitor”, or Android Studio and view the messages on the device. Some things can only be tested on a device and this is a good way to debug your code.
Next, depending on the version of Corona SDK you’re running, you can re-assign the print statement to do something differently. We had some daily builds that blocked this feature but we’ve backed it out for now until we can figure out how to support it better. But for now you can do:
local debugMode = true local originalPrint = print print = function( ... ) if debugMode then originalPrint( unpack( arg ) ) end end
Please do not use the variable “debug”, it’s an important global variable.
It’s better to make the new print function local took but then you have to define it in all modules.
Rob
Then before you deploy a production build you can set your value of debugMode to false and it will stop your prints from showing in the console log.
I haven’t try but i think it didn’t remove bug when we concate inside the print(value…value) and a value is boolean or nil.
Trying to concatenate a nil to a string is an error in your code that would need to be fixed. The solution is to either test the values outside of the print and only concatenate them if they are not nil then print the result or don’t concatenate them, but use a comma separator.
Either:
local valueToPrint = "" if value1 ~= nil then valueToPrint = valueToPrint .. value1 end if value2 ~= nil then valueToPrint = valueToPrint .. value2 end print( valueToPrint )
or
print( value1, value2 )Thank you