We're utilizing Cisco Web Communicator components from within chrome extension for several years
After switching to SDK 11.8.2 it is observed that initialization of SDK takes awhile.
What was found is:
1. initialize() call leads to invocation of Cisco Web Communicator extension
2. Cisco Web Communicator extension uses chrome.management.get() call in order to get extension name
for payload to be passed into Cisco Web Communicator native components
3. chrome.management.get() is async call, but Cisco Web Communicator extension never waits for
its completion and passes empty name as part of payload for Cisco Web Communicator native component
4. Cisco Web Communicator native component does not like that and triggers following entry in its log
===
2019-03-19 14:47:53,848 ERROR [0x00006b44] [src\jsdk\src\ClientManager.cpp(318) ] [webuc] [webuc::ClientManager::run] - Syntax error: parseChannelClientMessage ChannelClientMessage parsing failed. Error: Object with name: name does
n't exist. [{"ciscoChannelMessage":{"ciscoSDKClientMessage":{"name":"init","messageId":"0"},"client":{"id":"150968.101","url":"chrome-extension://cpaaimhcipgeaogdbdieicgfjbingani/","hostname":"cpaaimhcipgeaogdbdieicgfjbingani","type":"
Chrome"}}}]
===
5. Strangely enough if initialization attempt is being retried for at least a period of 90seconds, eventually SDK gets initialized.
6. This delay on initial load is however considered as a big issue by one of our customers
7. The only proper way of addressing this we would assume is to wait for chrome.management.get() completion before
connective it to a native port.
8. For the reference, versions of components being used:
Cisco Web Communicator extension: 3.1.0.363
Cisco Web Communicator: 11.8.2.254458
9. This problem is observed only in case if Cisco Web Communicator is being utilized from chrome extension.
