Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about how to solve the failure to create CloudDB object types. Many people may not know much about it. In order to make you understand better, the editor summarizes the following contents. I hope you can get something according to this article.

1. Prompt that the number of ObjectType does not match

NaturalBase: GenerateDiffSchemas: remove ObjectType is not supported. Count of ObjectType is less than curren

2. Object type negotiation failed

E/NaturalBase: OpenNaturalStore: negotiate failed.W/AGConnectCloudDB: openCloudDBZone: failed to create or open a cloudDBZone.

3. Scheme is not synchronized

[NaturalCloudSyncModule] [OnConnected]: negotiate schema. [PushMessageAndNotifyStoreCv] Schema is UnSynced

4. ObjectType version has been modified, but ObjectType has not been modified.

E/NaturalBase: CreateObjectType: ObjectType version has changed, but ObjectType has not changed.E/AGConnectCloudDB: createObjectType: failed to createObjectType into the AGCConnectCloudDB. Cause of the problem

The main reason for this problem is that the file corresponding to the ObjectType version in your Android project is inconsistent with the object type on the cloud side of AGC.

For the cloud side of AGC, you can check it here:

In the Android project, we mainly look at ObjectTypeInfoHelper and its corresponding Class.

Problem solving three axes: 1. Re-export ObjectTypes on the AGC cloud side

The biggest reason for this problem is the inconsistency between the ObjectType and the cloud side of the project. At this point, you need to re-export:

In the AGC interface, under: my Project-build-Cloud Database path, click the object types tab, select the version you want to export after the version, and then click Export.

When exporting, select JAVA-android and enter a package name.

After the export is complete, extract the files in zip to your project path.

2. Check the corresponding matching version

That is, in the ObjectTypeInfoHelper file

1. FORMAT_VERSION: it needs to correspond to the SDK version.

When the exported FORMAT_VERSION = 1, use the SDK of CloudDB below 1.2.2. It is recommended to use * 1.2.1.301

2 、 OBJECT_TYPE_VERSION

This is the Version selected on the ObjectType when exporting in the AGC interface. Generally, the export does not need to be modified.

After reading the above, do you have any further understanding of how to solve the failure of CloudDB object type creation? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.