[ 
https://issues.apache.org/jira/browse/CB-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211095#comment-16211095
 ] 

Radek Matěj commented on CB-13464:
----------------------------------

Yes, logging to Xcode and Safari works. It's just the System Log of Simulator 
with iOS11.

According to [this 
comment|https://github.com/NativeScript/nativescript-cli/issues/3118#issuecomment-332757300],
 it seems that there are changes in event logging in iOS11. Doesn't it mean 
that console.log should be propagated differently for iOS 11? And what about 
that _assertion failed_? This is actually the only and last message from the 
Cordova app.

> System Log does not work for Simulator with iOS 11
> --------------------------------------------------
>
>                 Key: CB-13464
>                 URL: https://issues.apache.org/jira/browse/CB-13464
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-ios
>         Environment: macOS 10.13; Xcode 9.0; [email protected]
>            Reporter: Radek Matěj
>            Assignee: Suraj Pindoria
>            Priority: Minor
>
> When running Cordova app on Simulator with iOS 11, console.log does not 
> appear in System Log.
> - it works in Safari dev tools console
> - it works when deploying to a simulator with iOS 10.3
> - the only record from the app in System Log for iOS 11 is:
> {code}
> HelloCordova[39532]: assertion failed: 17A405 15A372: libxpc.dylib + 69578 
> [D870A237-D3A7-31F5-AAD4-CE880C0C8E7B]: 0x7d
> {code}
> Steps to reproduce:
> - create and run empty Cordova project in Simulator:
> {code}
> cordova create test
> cd test
> cordova platform add ios
> cordova emulate --target="iPhone-6, 11.0" # vs cordova emulate 
> --target="iPhone-6, 10.3"
> {code}
> - open log (Debug → Open System Log...)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to