There was a bug introduced in Kii Cloud API in the following times in each site. Because of this issue, a custom attribute of users or things (document) in your application could have been corrupted.

Singapore Site: Feb 20 10:28:34 - Mar 2 06:20:05 (UTC)

Japan Site : Feb 21 09:07:03 - Mar 2 06:34:45 (UTC)

US Site : Feb 22 05:35:56 - Mar 2 06:16:00 (UTC)

EU Site : Feb 22 05:53:53 - Mar 2 06:21:14 (UTC)

Who were affected

Your application's users or things that fall under the following conditions were affected by the issue:

Users who have nested JSON objects or arrays in the user's custom attribute and haveexecuted the password reset or email / phone number verification inthe above-mentioned time.

Things that have nested JSON objects or arrays in its customattribute and have been executed the thing password change in theabove-mentioned time by the developer (you)

You can check the time the password reset or verification was executed by filtering devlog with keyword "verify" or "password" (document or you can access to "DevLog Viewer" from "Labs" tab in our Developer Portal).

The following applications should not have been affected by this issue.

Applications that don't use a nested JSON object nor array in the attribute of User or Thing.

Applications that don't use email / phone number verification and that don't use password reset feature.

Applications that is created in "cn3" site.

If you are not sure, please ask support@kii.com with your application's app-id.

Impact

Nested JSON object was converted to a single string, which is a JSON representation of the original object.A example is as follows,

Before affected

{ "a": 0, "b" : {"b1" : 1, "b2" : "b"} "c" : [1, 2, 3, 4]}

After affected

{ "a": 0, "b": "{\"b1\" : 1, \"b2\" : \"b\"}" "c" : "[1,2,3,4]"}

Fix of affected data

If you identified that the user or thing is affected but the number of the affected attributes is small, you can directly fix the custom attributes on the user console (document). If there are too many affected users and you can't fix manually, please contact to support@kii.com.

You think your application is suffered by this issue but not sure when you have executed the reset or verification, please contact to support@kii.com.

We deeply apologize for introducing this issue and also the for the delay of the announcement. We will keep trying hard to prevent this issue happen again.