No release notes added this week.
No release notes added this week.
This week we added release notes for Cloud Platform.
Cloud Platform
Release type | Environment(s) | Feature | Summary | |
---|---|---|---|---|
1 | Fixed | US-Dev | Device Service | Fixed an issue wherein unique properties API was returning incomplete unique property name. After the fix, the desired complete property name is retrieved. |
2 | Enhanced | US-Dev | User Service | This enhancement allows OEM customers to use their own custom URLs in emails for account confirmation and resetting password. |
3 | Enhanced | US-Dev | User Service | This enhancement will improve the end-user experience by allowing OEMs to use Device Name instead of DSN in device share email. |
This week we added release notes for Cloud Platform.
Cloud Platform
Release type | Environment(s) | Feature | Summary | |
---|---|---|---|---|
1 | Enhanced | US-Dev | Ayla Message Service | We added support to enter priority and lifespan/time-to-live (ttl) attributes in push notifications for Android (FCM) and iPhones (APNs). Please refer Create Destination. |
2 | Enhanced | US-Dev | ICC Service | We have enabled Data Search API to search devices. Please note, we have retained the ICC search module through blacklisting configuration. |
This week we added release notes for Cloud Platform.
Cloud Platform
Release type | Environment | Feature | Summary | |
---|---|---|---|---|
1 | Enhanced | Owlet-Field | Ayla Message Service | Effective June 1, 2023, international long codes are not allowed in the UK. To adhere to these regulatory changes, we have enabled the alphanumeric sender ID “NOTIFIER” to send messages (SMS) to the UK. |
2 | Enhanced | Owlet-Field | Insights - Transactions | SMS transaction counts are added in the Transactions tab of the Insights dashboard. |
3 | Fixed | US-Dev | Device Service | Fixed an issue wherein template association with device failed due to duplicate schedules. |
4 | Enhanced | Shark-Field | ICC Service | We have optimized the ICC OTA job success rate by prioritizing online devices for the updates. |
5 | Fixed | US-Field | Ayla Message Service | Fixed an issue wherein Get destinations API result was displayed in ascending order instead of descending order. After the fix, by default the result is displayed in descending order. |
6 | Fixed | US-Field | Rules Service | Fixed an issue wherein Get actions API was producing error when “is_internal= true” and “paginated=true”. Also, now by default the API result is displayed in descending order. |
7 | Best practices | US-Field | Rules Service | For Get actions and Get rules APIs, the response parameter “totalPages” is changed to “total_pages”. |
This week we added release notes for Cloud Platform.
Cloud Platform
Release type | Environment | Feature | Summary | |
---|---|---|---|---|
1 | Fixed | US-Dev | ICC Service | We have optimized the ICC OTA job success rate by prioritizing online devices for the updates. |
2 | Enhanced | US-Dev | Ayla Message Service | Additional phone number validations are added to identify invalid phone numbers. |
3 | Enhanced | US-Dev | Insights - Transactions | SMS transaction counts are added in the Transactions tab of the Insights dashboard. |
4 | Enhanced | US-Dev | Ayla Message Service | Effective June 1, 2023, international long codes are not allowed in the UK. To adhere to these regulatory changes, we have enabled the alphanumeric sender ID “NOTIFIER” to send messages (SMS) to the UK. |
No release notes added this week.
This week we added release notes for Cloud Platform.
Cloud Platform
Release type | Environment | Feature | Summary | |
---|---|---|---|---|
1 | Fixed | EU-Field | Ayla Device Service | Fixed an issue wherein incorrect logs were displayed. |
2 | Enhanced | US-Dev | Ayla Message Service | Effective April 25, 2023, dynamic Alphanumeric Sender IDs are not allowed in Australia. To adhere to these regulatory changes, we have enabled the registered alphanumeric sender ID “NOTIFIER” to send messages (SMS) to Australia. |
This week we added release notes for Cloud Platform.
Cloud Platform
Release type | Environment | Feature | Summary | |
---|---|---|---|---|
1 | Enhanced | US-Dev | Ayla Message Service (AMS) | This enhancement enables AMS to validate Apple Push Notification service (APNs) certificate of OEM applications before sending push notifications. An appropriate alert (in Alert History) is generated if APNs certificate is expired or unavailable for your application. Based on this alert you can take the required action (for example: renew certificate). |
2 | Enhanced | US-Dev | AMS | For the Get Destinations API, we updated the response body by adding new parameter “totalPages”. This parameter provides total number of pages generated when you run this API. |
3 | Fixed | US-Dev | AMS | Fixed an issue wherein Alert History was wrongly showing that the Push Notifications were delivered even when the notifications were not delivered due to unavailability/expiry of APNs certificate. |
4 | Enhanced | US-Field | Dynamic Firebase Linking | This enhancement will allow OEMs to customize the Account confirmation page by providing their own success URL. With this, end-users will be redirected to the OEM provided page instead of the default success page provided by Ayla. |
5 | Fixed | US-Field | Ayla Device Service | Fixed an issue wherein associating templates with devices was failing because of duplicate schedules. |