On Android you can set the maxLogcatObjectSize option in the app/package.json

  "android": {
    "v8Flags": "--expose_gc",
    "markingMode": "none",
    "maxLogcatObjectSize": 10000
  },

On iOS - I'm not aware of a flag, but you can check the logs in the chrome debugger, and it should not truncate them!

Looked into this again today, Apple's NSLog that now uses os_log under the hood has a hard limit at 1024 bytes, anything over that gets truncated. There's not easy way around it at this point - the chrome debugger is still unaffected, since it's not going through NSLog/os_log.

Will think about an alternative, but low priority.

@rigor789 here is a simple workaround for iOS https://stackoverflow.com/questions/17280264/maximum-size-a-nslog-can-print#42674570

@farfromrefug don't think that would work - but can certainly try it. The main issue why I think it wouldn't work is because it may not be printed the same way (the syslog style) and the CLI wouldn't see the logs.

not sure but I know o do see syslogs when running app on device.

I'm going to keep this open as the referenced PR improves some things but there's more that can be done here.

@NathanWalker what s the relation here? how does the params for logs fixes this one?

@NathanWalker what s the relation here? how does the params for logs fixes this one?

Not much relation other than log related. It was referenced on pr and auto close on merge, thus why I reopened this.

@NathanWalker ok sorry misunderstood