Repository navigation
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
rigor789
force-pushed
the
feat/ios-stdio-forwarding
branch
from
October 30, 2026 19:29
2665f9c to
8715264
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.