I’m using `Intercom(“showArticle”, articleId)` to show article content inside the Intercom widget. 

Under certain circumstances, after calling `Intercom(‘showArticle’,  articleId)`, instead of seeing the expected article, I instead get a “broken” version of the home screen. In particular, 

1. The bottom navigation tabs are missing
2. The help article links are inactive (clicking them does nothing)

My best theory so far is that there’s a race condition in the widget between loading the home screen content and the article content. My evidence to support this theory is

1. The “broken” home state opens in the article frame (wide container, no navigation tabs)
2. This state only (or exceedingly often) happens when calling `showArticle` before the messenger has been opened during the session. In that case, I believe `showArticle` is first loading/rendering the homescreen, increasing the likelihood of a race condition. 
3. I can eliminate the bug by changing my article link onclick to `Intercom('show'); setTimeout(() => {Intercom('showArticle', '{{ id }}')}, 2000);`. This opens the messenger and gives it time to load before showing the article. 
4. I’m much more likely to see the bug with “Disable cache” checked in chrome dev tools. 
5. I’ve seen a case where the article content does show, but then clicking the “back” button in the widget closes the widget entirely. The expected behavior seems to be that clicking back from the article detail goes back to the home screen. When I observe “back” closing the widget entirely, it seems like maybe the widget wasn’t able to load the home screen content and add it to the navigation stack properly. 

This appears related to, albeit not identical to, this thread.