Update to newly built Kotlin Client from GH Run 271

build-jar.gradle

@@ -6,7 +6,7 @@ plugins {
 
 jar {
 	archiveBaseName = 'cumulocity-clients-kotlin'
-	archiveVersion =  '10.18.0-270'
+	archiveVersion =  '10.18.0-271'
 }
 
 repositories {
@@ -18,7 +18,7 @@ publishing {
 		maven(MavenPublication) {
 			groupId = 'com.cumulocity'
 			artifactId = 'cumulocity-clients-kotlin'
-			version = '10.18.0-270'
+			version = '10.18.0-271'
 			from components.java
 		}
 	}

build.gradle

@@ -26,7 +26,7 @@ android {
     defaultConfig {
         minSdkVersion 19
 		targetSdkVersion 33
-		versionCode 270
+		versionCode 271
 		versionName "10.18.0"
 
 		testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"

src/main/java/com/cumulocity/client/api/AlarmsApi.kt

@@ -153,7 +153,7 @@ interface AlarmsApi {
 	 * * HTTP 202 An alarm collection is being updated in background.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 403 Not authorized to perform this operation.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 * @param xCumulocityProcessingMode
@@ -235,7 +235,7 @@ interface AlarmsApi {
 	 * * HTTP 201 An alarm was created.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 403 Not authorized to perform this operation.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 * @param xCumulocityProcessingMode
@@ -254,7 +254,7 @@ interface AlarmsApi {
 	 * 
 	 * Remove alarm collections specified by query parameters.
 	 * 
-	 * > **⚠️ Important:** Note that it is possible to call this endpoint without providing any parameter - it will result in deleting all alarms and it is not recommended.Also note that DELETE requests are not synchronous. The response could be returned before the delete request has been completed.
+	 * > **������ Important:** Note that it is possible to call this endpoint without providing any parameter - it will result in deleting all alarms and it is not recommended.Also note that DELETE requests are not synchronous. The response could be returned before the delete request has been completed.
 	 * 
 	 * ##### Required roles
 	 * 
@@ -349,7 +349,7 @@ interface AlarmsApi {
 	 * 
 	 * Update a specific alarm by a given ID.Only text, status, severity and custom properties can be modified. A request will be rejected when non-modifiable properties are provided in the request body.
 	 * 
-	 * > **ⓘ Info:** Changes to alarms will generate a new audit record. The audit record will include the username and application that triggered the update, if applicable. If the update operation doesn’t change anything (that is, the request body contains data that is identical to the already present in the database), there will be no audit record added and no notifications will be sent.
+	 * > **ⓘ Info:** Changes to alarms will generate a new audit record. The audit record will include the username and application that triggered the update, if applicable. If the update operation doesn���t change anything (that is, the request body contains data that is identical to the already present in the database), there will be no audit record added and no notifications will be sent.
 	 * 
 	 * ##### Required roles
 	 * 
@@ -363,7 +363,7 @@ interface AlarmsApi {
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 403 Not authorized to perform this operation.
 	 * * HTTP 404 Alarm not found.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 * @param id

src/main/java/com/cumulocity/client/api/ApplicationBinariesApi.kt

@@ -75,7 +75,7 @@ interface ApplicationBinariesApi {
 	 * 
 	 * Upload an application attachment (by a given application ID).
 	 * 
-	 * For the applications of type “microservice” and “web application” to be available for Cumulocity IoT platform users, an attachment ZIP file must be uploaded.
+	 * For the applications of type ���microservice��� and ���web application��� to be available for Cumulocity IoT platform users, an attachment ZIP file must be uploaded.
 	 * 
 	 * For a microservice application, the ZIP file must consist of:
 	 * 

src/main/java/com/cumulocity/client/api/ApplicationsApi.kt

@@ -24,7 +24,7 @@ import com.cumulocity.client.model.ApplicationCollection
 /**
  * API methods to retrieve, create, update and delete applications.
  * 
- * ### Application names
+ * ###��Application names
  * 
  * For each tenant, Cumulocity IoT manages the subscribed applications and provides a number of applications of various types.In case you want to subscribe a tenant to an application using an API, you must use the application name in the argument (as name).
  * 
@@ -130,7 +130,7 @@ interface ApplicationsApi {
 	 * * HTTP 201 An application was created.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 409 Duplicate key/name.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 * @param xCumulocityProcessingMode
@@ -209,7 +209,7 @@ interface ApplicationsApi {
 	 * 
 	 * Delete an application (by a given ID).This method is not supported by microservice applications.
 	 * 
-	 * > **ⓘ Info:** With regards to a hosted application, there is a caching mechanism in place that keeps the information about the placement of application files (html, javascript, css, fonts, etc.). Removing a hosted application, in normal circumstances, will cause the subsequent requests for application files to fail with an HTTP 404 error because the application is removed synchronously, its files are immediately removed on the node serving the request and at the same time the information is propagated to other nodes – but in rare cases there might be a delay with this propagation. In such situations, the files of the removed application can be served from those nodes up until the aforementioned cache expires. For the same reason, the cache can also cause HTTP 404 errors when the application is updated as it will keep the path to the files of the old version of the application. The cache is filled on demand, so there should not be issues if application files were not accessed prior to the delete request. The expiration delay of the cache can differ, but should not take more than one minute.
+	 * > **ⓘ Info:** With regards to a hosted application, there is a caching mechanism in place that keeps the information about the placement of application files (html, javascript, css, fonts, etc.). Removing a hosted application, in normal circumstances, will cause the subsequent requests for application files to fail with an HTTP 404 error because the application is removed synchronously, its files are immediately removed on the node serving the request and at the same time the information is propagated to other nodes ��� but in rare cases there might be a delay with this propagation. In such situations, the files of the removed application can be served from those nodes up until the aforementioned cache expires. For the same reason, the cache can also cause HTTP 404 errors when the application is updated as it will keep the path to the files of the old version of the application. The cache is filled on demand, so there should not be issues if application files were not accessed prior to the delete request. The expiration delay of the cache can differ, but should not take more than one minute.
 	 * 
 	 * ##### Required roles
 	 * 
@@ -265,7 +265,7 @@ interface ApplicationsApi {
 	 * 
 	 * * HTTP 201 An application was copied.
 	 * * HTTP 401 Authentication information is missing or invalid.
-	 * * HTTP 422 Unprocessable Entity – method not supported
+	 * * HTTP 422 Unprocessable Entity ��� method not supported
 	 * 
 	 * @param id
 	 * Unique identifier of the application.

src/main/java/com/cumulocity/client/api/BinariesApi.kt

@@ -106,8 +106,8 @@ interface BinariesApi {
 	 * 
 	 * Uploading a file (binary) requires providing the following properties:
 	 * 
-	 * * `object` – In JSON format, it contains information about the file.
-	 * * `file` – Contains the file to be uploaded.
+	 * * `object` ��� In JSON format, it contains information about the file.
+	 * * `file` ��� Contains the file to be uploaded.
 	 * 
 	 * After the file has been uploaded, the corresponding managed object will contain the fragment `c8y_IsBinary`.
 	 * 
@@ -121,7 +121,7 @@ interface BinariesApi {
 	 * The following table gives an overview of the possible response codes and their meanings:
 	 * 
 	 * * HTTP 201 A file was uploaded.
-	 * * HTTP 400 Unprocessable Entity – invalid payload.
+	 * * HTTP 400 Unprocessable Entity ��� invalid payload.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 403 Not authorized to perform this operation.
 	 * 

src/main/java/com/cumulocity/client/api/ChildOperationsApi.kt

@@ -225,7 +225,7 @@ interface ChildOperationsApi {
 	 * * HTTP 204 Child additions were removed.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 404 Managed object not found.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 * @param id
@@ -481,7 +481,7 @@ interface ChildOperationsApi {
 	 * * HTTP 204 Child assets were removed.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 404 Managed object not found.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 * @param id
@@ -737,7 +737,7 @@ interface ChildOperationsApi {
 	 * * HTTP 204 Child devices were removed.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 404 Managed object not found.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 * @param id

src/main/java/com/cumulocity/client/api/CurrentUserApi.kt

@@ -57,14 +57,16 @@ interface CurrentUserApi {
 	 * 
 	 *  ROLE_USER_MANAGEMENT_OWN_READ *OR* ROLE_SYSTEM 
 	 * 
+	 * Users with ROLE_SYSTEM are not allowed to query with Accept header `application/vnd.com.nsn.cumulocity.user+json`
+	 * 
 	 * ##### Response Codes
 	 * 
 	 * The following table gives an overview of the possible response codes and their meanings:
 	 * 
 	 * * HTTP 200 The request has succeeded and the current user is sent in the response.
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 */
-	@Headers("Accept:application/vnd.com.nsn.cumulocity.error+json, application/vnd.com.nsn.cumulocity.currentuser+json")
+	@Headers("Accept:application/vnd.com.nsn.cumulocity.error+json, application/vnd.com.nsn.cumulocity.currentuser+json, application/vnd.com.nsn.cumulocity.user+json")
 	@GET("/user/currentUser")
 	fun getCurrentUser(
 	): Call<CurrentUser>
@@ -85,7 +87,7 @@ interface CurrentUserApi {
 	 * 
 	 * * HTTP 200 The current user was updated.
 	 * * HTTP 401 Authentication information is missing or invalid.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 */
@@ -101,7 +103,7 @@ interface CurrentUserApi {
 	 * 
 	 * Update the current user's  password.
 	 * 
-	 * > **⚠️ Important:** If the tenant uses OAI-Secure authentication, the current user will not be logged out. Instead, a new cookie will be set with a new token, and the previous token will expire within a minute.
+	 * > **������ Important:** If the tenant uses OAI-Secure authentication, the current user will not be logged out. Instead, a new cookie will be set with a new token, and the previous token will expire within a minute.
 	 * 
 	 * ##### Required roles
 	 * 
@@ -113,7 +115,7 @@ interface CurrentUserApi {
 	 * 
 	 * * HTTP 200 The current user password was updated.
 	 * * HTTP 401 Authentication information is missing or invalid.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 */
@@ -217,7 +219,7 @@ interface CurrentUserApi {
 	 * * HTTP 401 Authentication information is missing or invalid.
 	 * * HTTP 403 Invalid verification code.
 	 * * HTTP 404 Cannot validate TFA TOTP code - user's TFA TOTP secret does not exist.
-	 * * HTTP 422 Unprocessable Entity – invalid payload.
+	 * * HTTP 422 Unprocessable Entity ��� invalid payload.
 	 * 
 	 * @param body
 	 */

src/main/java/com/cumulocity/client/api/DeviceCredentialsApi.kt

@@ -22,7 +22,7 @@ import com.cumulocity.client.model.BulkNewDeviceRequest
  * 
  * Device credentials can be enquired by devices that do not have credentials for accessing a tenant yet.Since the device does not have credentials yet, a set of fixed credentials is used for this API.The credentials can be obtained by [contacting support](https://cumulocity.com/guides/about-doc/contacting-support/).
  * 
- * > **⚠️ Important:** Do not use your tenant credentials with this API.
+ * > **������ Important:** Do not use your tenant credentials with this API.
  * > **ⓘ Info:** The Accept header should be provided in all POST requests, otherwise an empty response body will be returned.
  */
 interface DeviceCredentialsApi {
@@ -91,7 +91,7 @@ interface DeviceCredentialsApi {
 	 * 
 	 * A separator is automatically obtained from the CSV file. Valid separator values are: `\t` (tabulation mark), `;` (semicolon) and `,` (comma).
 	 * 
-	 * > **⚠️ Important:** The CSV file needs the "com_cumulocity_model_Agent.active" header with a value of "true" to be added to the request.
+	 * > **������ Important:** The CSV file needs the "com_cumulocity_model_Agent.active" header with a value of "true" to be added to the request.
 	 * > **ⓘ Info:** A bulk registration creates an elementary representation of the device. Then, the device needs to update it to a full representation with its own status. The device is ready to use only after it is updated to the full representation. Also see [credentials upload](https://cumulocity.com/guides/users-guide/device-management/#creds-upload) and [device integration](https://cumulocity.com/guides/device-sdk/rest/#device-integration).
 	 * A CSV file can appear in many forms (with regard to the optional tenant column and the occurrence of device information):
 	 * 

src/main/java/com/cumulocity/client/api/DevicePermissionsApi.kt

@@ -35,7 +35,7 @@ import com.cumulocity.client.model.DevicePermissionOwners
  * 
  * The wildcard "*" enables you to access every API and stored object regardless of the fragments that are inside it.
  * 
- * > **⚠️ Important:** If there is no fragment in an object, for example, to read the object, you must use the wildcard "*" for the **fragment_name** part of the device permission (see the structure above). For example: `"10200":["MEASUREMENT:*:READ"]`.
+ * > **������ Important:** If there is no fragment in an object, for example, to read the object, you must use the wildcard "*" for the **fragment_name** part of the device permission (see the structure above). For example: `"10200":["MEASUREMENT:*:READ"]`.
  */
 interface DevicePermissionsApi {