Skip to main content

98 posts tagged with "✅ Fixed"

Changes related to bug fixes

View All Tags

Service API v2.4.1

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Client API v1.8.3

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Service API v2.3.2

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Client API v1.7.5

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like é resulted in é. They are now encoded correctly.

Service API v2.2.3

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Client API v1.6.11

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Service API v2.1.9

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Client API v1.5.4

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Service API v2.0.10

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.

Client API v1.4.4

Fixed an issue with the encoding of special characters. They were not encoded correctly when retrieved. Cases like 'é' resulted in 'é'. They are now encoded correctly.