Skip to main content

98 posts tagged with "✅ Fixed"

Changes related to bug fixes

View All Tags

Service API v2.1.5

Fixed issue where messages, that should be send to other Services, were not send via our asynchronous Queue.
Which means that if the receiving Service is "slow", your api call would be slow aswell.

Example:
POST /users/{userId}/messages sends a message to the Client and connected Services.
If the connected Service is slow and responds after 1 second, your POST /users/{userId}/messages call would take ~ 1 second.

Now it doesn't matter if the connected Service is slow, because POST /users/{userId}/messages will put the message into a Queue which sends the message asynchronous to the connected Service. Resulting in your api call only taking a couple ms.

More info about the Queuing mechanism

Admin API v1.1.0

Features

  • It is now possible to change the Default service for your Parley account using this new endpoint
  • When the admin-api cannot connect to the Database, for whatever reason, it now shows a descriptive error instead of a white screen.
  • We've added multiple headers to improve Security
    • X-XSS-Protection: 1; mode=block Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected.
    • X-Content-Type-Options: nosniff Prevents MIME-sniffing
    • X-Frame-Options: SAMEORIGIN The page can only be displayed in a frame on the same origin as the page itself
  • When creating a new account you can now supply the demo value which, if true, will make sure this account is correctly configured for use in the mobile Parley Demo app (android/ios)

Fixes

  • When using the GET /accounts/users endpoint, we would only return 10 users. Now we return all of the users.

Service API v2.1.3

Fixed issue where if we needed to Push something to the Clients, we would put those messages into a queue but they wouldn't get picked up directly.
Now when something enters the queue it gets picked up immediately.

This should increase performance on the sending of push notifications to clients.

info

When a Client has more than 3 devices, we will only push directly to the newest 3 devices.

Service API v2.0.7

Fixed issue where if we needed to Push something to the Clients, we would put those messages into a queue but they wouldn't get picked up directly.
Now when something enters the queue it gets picked up immediately.

This should increase performance on the sending of push notifications to clients.

info

When a Client has more than 3 devices, we will only push directly to the newest 3 devices.