Client API v1.1.4
- Fixed an issue which was preventing some devices from receiving push notifications.
This issue was temporarily fixed on 26-06-2020 around 19:00, but has now made it's way into an official release.
Changes related to bug fixes
View All TagsFixed an issue where push notifications wouldn't get send to the client's devices.
POST /messages calls to the API that contains the full url of the current page. Normally this information is found in the referer header, but Chrome is changing the content of this header to contain only the domain of the website you are on. (the API doesn't do anything with this new param yet, we are working on this)inviteNotificationSendButton setting was true (due to the naming of the setting this was expected behaviour, but it wasn't very practical to only allow turning this feature on in the inviteNotification screen)Added
Fixed
document.contains() doesn't exists in IE11, document.body.contains() does)Array.from() doesn't exists so i added the core-js es.array.from module polyfillThere is an issue in this version which prevents IE 11 to load the chat. This is fixed in v1.2.17
Added
sendMessage(), which is a rename of sendInitialMessage() since it is not only usable for the initial message. referencetype param to sendMessage(): referenceparentNode: referenceImproved
Fixed
Deprecated
sendInitialMessage function since it is now replaced by the sendMessage which is an identical replacementFixed bug where the interval of Polling would be reset every time a INFO message was received by the chat. Now it only resets on all new messages except INFO messages.
parleySettings.eventswindow.parleySettings object send out events whenever a value changes. Our Proxy polyfill was conflicting with other Proxy polyfills on the website our chat was implemented on. Our Proxy polyfill now gets called as ParleyProxy() instead of Proxy().Added
serviceUnreachableNotification and serviceUnreachableNotificationAlertimageTooBig, imageFormatIncorrect and messageSendFailed[Google](www.google.com) in almost all texts inside the conversation windowevents. Here you can create a custom callback for the event events.onAuthorizationExpired. This callback is then called whenever the API returns that the client's authorizationHeader is expired.window.parleySettings.runOptions.showAgentName = false.userAdditionalInformation, more info on how to use it can be found in the docsImproved
grids)Fixed
: in front would fail, because it sees it as the protocol ex: "check: www.google.com" would fail "check www.google.com" would succeed. Now they both succeed.window.parleySettings.registerNewDevice() so that when you log-in that way, the "anonymous" messages are directly visible in the "non-anonymous" conversation.Removed
Improved
Fixed