Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-5054] Fastdev fills up logcat when ti.android.debug set to true in tiapp.xml

GitHub Issuen/a
TypeBug
PriorityLow
StatusClosed
ResolutionWon't Fix
Resolution Date2013-10-17T21:12:36.000+0000
Affected Version/sRelease 1.8.0
Fix Version/sn/a
ComponentsAndroid
Labelsfastdev, tbs-1.9.0
ReporterBill Dawson
AssigneeIngo Muschenetz
Created2011-08-19T10:18:19.000+0000
Updated2017-03-30T18:00:58.000+0000

Description

To recreate, make sure you have 
    <property type="bool" name="ti.android.debug">true</property>
in your tiapp.xml, and then also that fastdev is running (which it will do automatically if you launch from Titanium Studio.) Then when you're app is running, check adb logcat and you'll see the tons of messages streaming by. As we discussion, probably a new ti.android.log_level would be useful as part of the solution.

Comments

  1. Marshall Culpepper 2011-09-01

    To enable tracing for fastdev, use this adb command: 
       $ adb shell setprop log.tag.TiFastDev ASSERT
    If you send the "restart-app" command from fastdev, you should see the trace message Execute command: restart Afterward, you can set the log level back to INFO and the Execute command:.. log messages should go away: 
       $ adb shell setprop log.tag.TiFastDev INFO
  2. Bill Dawson 2011-09-01

    Reopening because of difficulties getting log level back to INFO.
  3. Ingo Muschenetz 2013-10-17

    We are deprecating FastDev in version 3.2.0, so marking this as "Won't Fix"
  4. Lee Morris 2017-03-30

    Closing ticket with reference to the above comment from Ingo.

JSON Source