I have an app (Freshchat) with a custom installation page and it’s location is conversation_user_info, running in production.
Every time I access it’s settings and change some parameter, just navigating back to conversation inbox and opening the app is not enough to get the updated parameters , I mean, calling client.iparams.get() does not give me the updated parameters.
To make it “refresh” it’s parameters, I need to perform a hard reload (CTRL + SHIFT +R in Chrome).
Although this is not a major bug, still gets us some trouble, since sometimes this parameters drives the app process.
If something could be done to hard refresh this info when updating the app settings, it would be great!
Any update on this?
Now I noticed this issue accessing the conversation thought the People menu, after searching for it on the search box.
And this case is worse because is not just the iparams that is not being loaded correctly, but here the Conversation Data (Conversation Data Method) is wrong, it’s returning the info about the last conversation opened on inbox.
This is a major bug for APPs that uses conversation context.
I followed the following steps to repoduce the issue for #2, but I wasn’t able to. Can you please correct me if I doing it correctly?
In my trail account there were 6 conversations.
I installed a custom app, that simply logs client.data.get("conversation") resolved promise with data holds context of current conversation. I specifically looked at message_parts and users attributes to verify.
I opened team inbox and simply navigated across conversations. I found the data received is correct as per current conversation.
As you have pointed out, I searched using search bar for a contact to open a conversation after updating an iparam in app configuration page.
The browser console logs suggests that iparams data is wrong until hard refresh needed but the conversation data via data method is correct.
So I will follow up on the iparams part (#1) of the topic, but can you let me know if I should be doing anything differently to reproduce #2 data method issue?
@samuelpares - I’ve reported this as a bug to product managers. The team has also confirmed it. Thank you so much for reporting this issue. The priority is determined by product managers. So at the moment I do not have any estimated timeline when fix could be planned.
It’s been more than one year and these 2 bugs still remains.
The critical one is the data method not returning the correct data when app is rendered in people page. If we can’t interact with the conversation data, there’s no reason for the app to be rendered in people page. If this is not going to be fixed, it should be removed the app rendering in people page.
Customers are using an app performing operations with wrong data.