Hello, I realized there was some buggy behavior with runningContext
only with production apps (when using a development clientID/secret, there is no error).
The error occurs when you click “open in meeting” after launching the app in the main client. It seems like the runningContext does not update to “inMeeting” and stays in “InMainClient”. It seems to just transport the app from the main client into the meeting client, and the context does not update.
Steps to Reproduce:
- Launch a production application from the app tiles.
- Click “Open in Meeting”
- View the
runningContext
and verify it still says “inMainClient” and not "inMeeting’.
Here is a video of my findings: incorrect runningContext.mov - Google Drive