Skip to main content

Hi Intercom team,

we at Center just doing our initial integration with your product and running into some problems with iOS SDK. In the documentation we found the following:

Surveys don't currently support real-time mobile events, meaning your app users won't receive the survey immediately after the event happens. The survey will only send when a user update is triggered:

  • A user launches your app,

  • A user closes your app and then opens it after a few moments, or

  • By updating the user via our mobile SDK methods.

So in our app we are trying to present Intercom survey at a specific point in time when a user performs a specific action. We did create and registered a specific event for this. According to the documentation above, a user update should force the survey to be presented. However, no matter what we tried, it did not work for us on iOS. It does work on Android though. 

Can you please clarify if this functionality is supported on iOS? Maybe there is an existing bug or a specific workaround.

Thank you,

Eugene

Hi ​@Eugene Gordin thanks for checking in! 🤝 

 

The first thing I would consider is your app version. Make sure were up to date with the latest version to ensure smooth sailing ⛴️ 

If the survey works on Android but not on iOS, verify that the iOS SDK is updated to the latest version. You can also try using the Intercom.presentContent method to manually trigger the survey. If issues persist, consider testing with the example iOS app provided by us to ensure the setup is correct ✅ 


Thank you so much Paul for your response. 

We did make sure that we are using the latest version of the SDK available as well as we did try to use presentContent functionality; however,  that functionality is not equivalent to custom events at least according to the behavior observed as well as Intercom documentation.

Is there a way to have a chat with engineering team?

 

Thank you!


@Eugene Gordin It’s Mat from the Support Engineering Team 😀

Sure you can start a conversation via Messenger in your workspace. It is a preferred way to address the SDK malfunctions.


Reply