Michi, in that scope-registry.log you pastebinned, it looks like the ZMQ socket is getting closed/removed in the middle of calling Query in the scope:
(process:2658): ubuntu-app-launch-DEBUG: Initialized Click DB
[2016-12-09 05:20:22.797] ERROR: clickscope: ObjectAdapter: error unmarshaling request header (id: , adapter: clickscope-c, op: ): ZmqReceiver::receive(): socket was closed
<messages from UAL as we query for apps>
[2016-12-09 05:20:22.807] ERROR: clickscope: ReplyImpl::error(): unity::scopes::MiddlewareException: Cannot invoke operations while middleware is stopped
I'm not sure why this would happen, and I didn't realize we need to handle exceptions in the middleware, within the scope itself. Any idea why the socket would be getting destroyed from the other end? This seems to be why the scope is blank.
Michi, in that scope-registry.log you pastebinned, it looks like the ZMQ socket is getting closed/removed in the middle of calling Query in the scope:
(process:2658): ubuntu- app-launch- DEBUG: Initialized Click DB :receive( ): socket was closed scopes: :MiddlewareExce ption: Cannot invoke operations while middleware is stopped
[2016-12-09 05:20:22.797] ERROR: clickscope: ObjectAdapter: error unmarshaling request header (id: , adapter: clickscope-c, op: ): ZmqReceiver:
<messages from UAL as we query for apps>
[2016-12-09 05:20:22.807] ERROR: clickscope: ReplyImpl::error(): unity::
I'm not sure why this would happen, and I didn't realize we need to handle exceptions in the middleware, within the scope itself. Any idea why the socket would be getting destroyed from the other end? This seems to be why the scope is blank.