So, I sorted out my issue, but I'm not sure why it worked. here's the code context.
I am using EmberJS to develop my embedded app. To aid in this, I've made an EmberJS Addon (found here, it's still a WIP) which essentially wraps the Embedded App SDK with Ember conventions to enable some data-binding in the templating engine.
When my app boots up, it initializes the addon, which in turn creates an instance of the SDK.
In ADDON:
this._webexInstance = new window.Webex.Application();
...which I then immediately setup the promise chain to respond to the onReady() event:
In ADDON:
this._webexInstance.onReady().then(() => { })
Once the instance reports that it's ready, I then go and fetch the user. Once the user is resolved, I then resolve the promise that was blocking my app from booting.
It was here that I was then calling "getMeeting()" to get the meeting details. Here's the high-level sequence.
In Addon: OnReady() -> onReadyHandler() -> context.getUser() -> context.getMeeting()
The change I made to get it to work was to remove the final step and call it, more deliberately from the consuming app:
In Addon: OnReady() -> onReadyHandler() -> context.getUser()
In my addon, I have an accessor function for the meeting details call, like this:
ADDON CODE:
_cachedMeetingPromise: undefined;
get meeting(): Promise<any>{
let retVal = this._cachedMeetingPromise ? this._cachedMeetingPromise : this.localDev ? Promise.resolve(this.fakedMeetingInfo) : this.context.getMeeting();
this._cachedMeetingPromise = retVal;
retVal.then((meetingInfo: any)=>{
this.currentRoles = meetingInfo.userRoles;
this._cachedMeetingPromise = undefined;
console.log("WEBEX for getMeetings: ", meetingInfo)
}).catch((error:any) =>{
this._cachedMeetingPromise = undefined;
// @ts-ignore
console.log("WEBEX ERROR for getMeetings: ", Webex.Application.ErrorCodes[error])
})
return retVal;
}
Which I then call in the consuming app like this:
APP CODE:
this.webex.meeting.then((meeting: any)=>{
this.websocket.connect(meeting);
}).catch((error)=>{
console.log("WEBEX IN APP: ERROR FOR GET MEETING", error);
})This seems to be working now. I suppose it's possible that the sequencing and timing between calls could have caused an issue.
