openFrameAPI.init() returns with error "Openframe init request timed out" in Chrome

[gavin17]

I've just updated to use openFrameAPI 1.0.2 for use with the OpenFrame 1.3.6 within ServiceNow Kingston.   When running in the latest Chrome 63.0.3239.132, after the first call of the init() method, as described here:

https://docs.servicenow.com/bundle/kingston-customer-service-management/page/app-store/dev_portal/AP...

the failureCallback with the error "Openframe init request timed out" will happen on all page reloads.   This happens on all Normal Reloads unless "Hard Reload" is explicitly used.

Using FireFox and Edge, the init() call returns and loads successfully and all reloads.

Has anyone else run into this issue and is there a fix?

[bernyalvarado]

Hi Gavin,

Could it be that your chrome browser is preventing the openFrame window from opening? Have you checked at the right of your browser's url navigation bar to see if there's an icon indicating that a new window/popup has been blocked?

Thanks,

Berny

[gavin17 · Accepted solution]

Hi Berny,

Thanks for the suggestion.   Actually, after escalating to ServiceNow developers, it appears this was a bug in Kingston Patch 0 which is addressed in Kingston Patch 1.   I've been able to confirm this is true when tested with a customer instance of Kingston Patch 1.   Unfortunately, Kingston Patch 1 is not yet available through developer.servicenow.com.  

It is beyond my understanding why Patch 1 has been released to customers before developers can test with their integrations...