NSLogger Viewer - xcode

is NSLogger Viewer working for anyone? I'm running Xcode8b6 and can't get any of the sample files to actually log something into the app.
I even rebuild NSLoggerViewer from scratch and when running it in the debug mode, it reports following issue:
2016-08-28 21:13:51.208393 NSLogger[32974:1208999] CFNetwork SSLHandshake failed (-9806)
2016-08-28 21:13:51.208580 NSLogger[32974:1208999] Stream error occurred: stream=<__NSCFInputStream: 0x6180001046e0> self=<LoggerNativeTransport 0x600000083390 listenerPort=63262 publishBonjourService=1 secure=1> error=Error Domain=NSOSStatusErrorDomain Code=-9806 " : t" UserInfo={_kCFStreamErrorCodeKey=4294957490, _kCFStreamErrorDomainKey=3}
2016-08-28 21:14:48.142366 NSLogger[32974:1208999] incoming connection
2016-08-28 21:14:48.143200 NSLogger[32974:1208999] setupSSLForStream, stream=<__NSCFInputStream: 0x610000104ec0> self=<LoggerNativeTransport 0x600000083390 listenerPort=63262 publishBonjourService=1 secure=1> serverCerts=(
"<SecIdentity 0x608000269440 [0x7fffe148cbd0]>",
"<cert(0x1005884d0) s: NSLogger self-signed SSL i: NSLogger self-signed SSL>"
)
Does anyone have any idea what's going on here?

Related

stream_socket_client(): SSL operation failed with code 1

stream_socket_client(): SSL operation failed with code 1. OpenSSL Error messages:
error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
I got error when I try to send a notification using Apple portal. Can you help me with global solutions.?

Bug CleverBeagle Pup 2.0 Meteor GraphQL deployment on Heroku

1) In the first time, when I deployed the origin code to heroku server with git clone https://github.com/cleverbeagle/pup
The launching application didn't work.
I managed to correct this with to copy the content of 'settings-development.json' file and paste in Heroku => myProject => Setttings => Reveal Config Vars => Key : METEOR_SETTINGS and Value : I pasted here the content.
thanks to :
- https://github.com/cleverbeagle/pup/issues/9
- https://github.com/cleverbeagle/pup/issues/197
So, now, the app is showing on server.
2) On Chrome console, I have this error :
50d72c91808ef7fba57f920b67d152d2d57698eb.js?meteor_js_resource=true:9 WebSocket connection to 'ws://localhost:4001/graphql' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
so I changed this in METEOR_SETTINGS
"graphQL": {
"httpUri": "http://localhost:3000/graphql",
"wsUri": "ws://localhost:4001/graphql"
},
to
"graphQL": {
"httpUri": "https://myproject.herokuapp.com:3000/graphql",
"wsUri": "wss://myproject.herokuapp.com:4001/graphql"
},
Note without https and wss, the app is not showing
3) Now on Chrome Console, I have :
this warning :
50d72c91808ef7fba57f920b67d152d2d57698eb.js?meteor_js_resource=true:9 WebSocket connection to 'wss://myproject.herokuapp.com:4001/graphql' failed: WebSocket is closed before the connection is established.
and after several warning above, I have this error :
50d72c91808ef7fba57f920b67d152d2d57698eb.js?meteor_js_resource=true:9 WebSocket connection to 'wss://myproject.herokuapp.com:4001/graphql' failed: WebSocket opening handshake timed out
By using the origin source code from Pup, I can signup on server but I cannot create a new document.
Any help, please ?
Thank you
EDIT 15 JAN 2019
**4) I remove Port like this : **
"httpUri": "https://myproject.herokuapp.com/graphql",
"wsUri": "wss://myproject.herokuapp.com/graphql"
Now, I can create New document on https://myproject.herokuapp.com/documents
but I still have this warning :
fe6fa1ac83e19aa2513ac3f97293600e8dc99e8e.js?meteor_js_resource=true:9
WebSocket connection to 'wss://myproject.herokuapp.com/graphql'
failed: WebSocket is closed before the connection is established.
and this error :
WebSocket connection to 'wss://myproject.herokuapp.com/graphql'
failed: Error during WebSocket handshake: Unexpected response code:
503
any idea ?
Thanks

Google Assistant Hotword Detection Not Working

I'm new to Google Assistant SDK. Recently I embedded Assistant to Raspberry Pi 3 B. I used the googlesamples-assistant-hotword sample. It worked fine. But next time I run the command I got some errors. I reinstall the sdk and tried, but got the same error. However googlesamples-assistant-pushtotalk still works. But googlesamples-assistant-hotword gives errors. How can I fix this. The errors I got are as follows;
(env) pi#raspberrypi:~$ googlesamples-assistant-hotword
ON_MUTED_CHANGED:
{u'is_muted': False}
ON_START_FINISHED
E0922 08:01:19.189206804 9868 handshake.c:128] Security handshake failed: {"created":"#1506047479.189164282","description":"Handshake read failed","file":"../../third_party/grpc/src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1506047479.189160249","description":"FD shutdown","file":"../../third_party/grpc/src/core/lib/iomgr/ev_epoll_linux.c","file_line":1045}]}
E0922 08:01:20.189959242 9868 handshake.c:128] Security handshake failed: {"created":"#1506047480.189916251","description":"Handshake read failed","file":"../../third_party/grpc/src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1506047480.189911706","description":"FD shutdown","file":"../../third_party/grpc/src/core/lib/iomgr/ev_epoll_linux.c","file_line":1045}]}
E0922 08:01:21.190931499 9868 handshake.c:128] Security handshake failed: {"created":"#1506047481.190904069","description":"Handshake read failed","file":"../../third_party/grpc/src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1506047481.190900454","description":"FD shutdown","file":"../../third_party/grpc/src/core/lib/iomgr/ev_epoll_linux.c","file_line":1045}]}
[9782:9800:ERROR:speech_recognition_activity.cc(550)] S3 connection has timed out: No data from S3

Upgrade to new XCode; can't built in Xamarin

I think that one of the last XCode upgrades that came in last week appears to have broken my Xamarin iOS builds. They fail with:
Failed to locate a valid instance of CoreSimulatorService in the bootstrap. Adding it now.
Or
.../SignInUniversalController_iPhone.storyboard: Error: 2016-07-31 12:11:38.046 ibtoold[23284:2756861] [MT] IBPlatformTool: *** Failed to launch tool with description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity:
Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity (Failure reason: Software caused connection abort): Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 (Failure reason: Failed to create SimDeviceSet at path /Users/eric/Library/Developer/Xcode/UserData/IB Support/Simulator Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator to see why creating the SimDeviceSet failed.): Failed to initialize simulator device set. (Failure reason: Failed to subscribe to notifications from CoreSimulatorService.): Error returned in reply to notification request: Connection invalid (Failure reason: Software caused connection abort)
2016-07-31 12:11:46.096 ibtoold[23284:2756861] [MT] IBPlatformTool: Wrote failed marshalling request diagnostics to path: /var/folders/t9/t9xl93t50ql14mr0lxmmw_2r0000gn/T/IB-agent-diagnostics_2016-07-31_12-11-46_067000
Error: Internal error. Please file a bug at bugreport.apple.com and attach "/var/folders/t9/t9xl93t50ql14mr0lxmmw_2r0000gn/T/IB-agent-diagnostics_2016-07-31_12-11-46_067000".
The logs mentioned in the first error message doesn't appear to be more verbose than the above:
Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity (Failure reason: Software caused connection abort): Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 (Failure reason: Failed to create SimDeviceSet at path /Users/eric/Library/Developer/Xcode/UserData/IB Support/Simulator Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator to see why creating the SimDeviceSet failed.): Failed to initialize simulator device set. (Failure reason: Failed to subscribe to notifications from CoreSimulatorService.): Error returned in reply to notification request: Connection invalid (Failure reason: Software caused connection abort)
Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSLocalizedDescription=Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fce44256b20> System content 1x for IBCocoaTouchFramework-NineOneAndLater w/ default fidelity, NSUnderlyingError=0x7fce44152c40 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSUnderlyingError=0x7fce441b8150 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo={NSLocalizedFailureReason=Failed to subscribe to notifications from CoreSimulatorService., NSLocalizedDescription=Failed to initialize simulator device set., NSUnderlyingError=0x7fce44155b00 {Error Domain=NSPOSIXErrorDomain Code=53 "Software caused connection abort" UserInfo=0x7fce441c31b0 (not displayed)}}}, NSLocalizedFailureReason=Failed to create SimDeviceSet at path /Users/eric/Library/Developer/Xcode/UserData/IB Support/Simulator Devices. You'll want to check the logs in ~/Library/Logs/CoreSimulator to see why creating the SimDeviceSet failed., NSLocalizedDescription=Failed to find a suitable device for the type SimDeviceType : com.apple.dt.Xcode.IBSimDeviceType.iPad-1x with runtime SimRuntime : 9.3 (13E230) - com.apple.CoreSimulator.SimRuntime.iOS-9-3}}}
This is an iPhone project, but uses a Universal component; I note that since the above says iPad.
When it fails, it opens up the Storyboard editor and it appears to be OK there; there's nothing that seems surprising at first glance.
XCode: Version 7.3.1 (7D1014)
Xamarin: Latest Stable; no updates available
Any insight or thoughts? Thanks!

HTTPS connection error on MAMP server

I have setup a MAMP server and configured an SSL site. I have verified it works with a call (https://app.dev:8890/login/hello.html) to a simple html file.
i found a test app that woks and connects to a remote server with no issues.
I modified the app to connect using my local MAMP server....
let url:NSURL = NSURL(string: "https://app.dev:8890/login/jsonsignup.php")!
when I run it and try getting to that page I receive this error....
2015-09-04 13:04:19.679 SwiftLoginScreen[14905:437125] PostData: username=uname&password=pword&c_password=pword
2015-09-04 13:04:19.693 SwiftLoginScreen[14905:441196] CFNetwork SSLHandshake failed (-9824)
2015-09-04 13:04:19.695 SwiftLoginScreen[14905:441196] CFNetwork SSLHandshake failed (-9824)
2015-09-04 13:04:19.697 SwiftLoginScreen[14905:441196] CFNetwork SSLHandshake failed (-9824)
2015-09-04 13:04:19.697 SwiftLoginScreen[14905:441196] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9824)
I do not want to disable ATS I just need to see where my issue is with this connection.

Resources