Repository navigation
Conversation
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
2665f9c to
8715264
Compare
8715264 to
4f05142
Compare
Without a console an app's stdio is /dev/null, so print() and, on devices, NSLog never reach any log stream, and a CLI can't attach to them after launch. In debug builds whose CLI sets forwardStdio in the app's package.json, with stdout still /dev/null, the runtime now pipes them into os_log under the org.nativescript.stdio subsystem. Long lines are split like console messages.
4f05142 to
c839e4a
Compare
What is the current behavior?
Without a console, an app's stdio is
/dev/null.print()output is lost, and so isNSLogon devices, where it only goes to stderr on iPadOS 26.7. A CLI can't attach to it after launch, because stdio is fixed when the process starts.What is the new behavior?
In debug builds whose CLI sets
forwardStdioin the app'spackage.json, with stdout still/dev/null, the runtime pipes stdout and stderr intoos_logunder theorg.nativescript.stdiosubsystem, withstdoutandstderras categories.print()would wait for a full buffer.NSLogthere also reaches the unified log and would print twice. That meansfputs(..., stderr)isn't forwarded on the simulator.Known limits: output buffered at the moment of a crash is lost, so the last lines before an
abort()may not appear. An unterminated final line isn't forwarded until a newline arrives or it reaches 64 KB.Testing
Demo app with Swift code calling
print()(short, 5,000 characters, background thread),NSLogandfputs(stderr), on both launches of each run:--log debug, simulatorprint()shown, 5,000-character line intact,NSLogonce (fromFoundation)--log debug, iPad (iPadOS 26.7)print(),NSLogand stderr all shown oncesimctl launch --console-ptyprint()goes to the console directlyOlder iOS versions weren't tested, and
NSLogmay behave differently there. A launch from Xcode itself wasn't tested either.Part of a stack
Base: #530. The CLI side is NativeScript/nativescript-cli#6181.
Summary by CodeRabbit