Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-27442

iOS: Investigate other means of debug logging simulator builds


    • Type: Improvement
    • Status: Open
    • Priority: None
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: iOS, Tooling
    • Labels:


      The strategy for relaying log messages from a Titanium app running from the iOS Simulator has evolved over the years.

      Titanium started by writing logs to a file and the CLI would tail the log file. In Titanium 6, this was replaced with a client/server system to reuse code between device and sim builds, but this causes complications for sim builds (TIMOB-27331).

      Titanium SDK 8.2.1 reverts this functionality back to file-based logging for sim builds.

      One concern is that apparently the file-based logging will not print messages from Swift code.

      This ticket is investigate logging from Swift code as well as using the Console app or simctl to relay the log messages.

      In macOS Sierra, the Console app added support for simulator apps. Now that we have ended support for macOS older than Sierra, we can now entertain the idea of relaying logs from the Console app.

      Need to look into streaming the output from xcrun simctl spawn <UDID> log stream.




            • Assignee:
              cbarber Chris Barber
              cbarber Chris Barber
            • Watchers:
              2 Start watching this issue


              • Created:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                  Git Integration