System.println on the real device?

Is debug / informative lines like System.println in app code performed on the real devices?

Is it slow done or take resources on the real device?

Should these lines will be commented or some technics like Logger (which recognises :debug :release states) should be used for optimal performance on the real devices?

Top Replies

jim_m_58 over 4 years ago in reply to Bodya +1

Also see the new developer FAQ. Check out some other stuff there, like app crashes when settings change

https://forums.garmin.com/developer/connect-iq/w/wiki/4/new-developer-faq#debugging.

println calls…

All Replies

0 Bodya over 4 years ago

it seems some answer is already here https://forums.garmin.com/developer/connect-iq/f/discussion/3678/writing-system-println-data-to-text-files-in-logs-folder

So, based on this it seems better to avoid unnecessary println in the production app on the real device.

0 jim_m_58 over 4 years ago in reply to Bodya

Also see the new developer FAQ. Check out some other stuff there, like app crashes when settings change

https://forums.garmin.com/developer/connect-iq/w/wiki/4/new-developer-faq#debugging.

println calls will chew up some memory, and using them with an app from the store is tricky as the store generates the name of the prg.