-
Type:
Task
-
Resolution: Fixed
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
6972
-
SDK FY21-Q3, SDK FY21-Q3.
Found with SyncedRealmTests#connectWithInitialSchema when trying to upgrade to latest test image in https://github.com/realm/realm-java/pull/6968
06-27 16:12:46.470 V/REALM_SYNC( 3481): Connection[2]: Session[2]: Transforming local changeset [1/1] through 15 incoming changeset(s) with 4 conflict group(s) 06-27 16:12:46.471 D/REALM_SYNC( 3481): Connection[2]: Session[2]: Finished transforming 1 local changesets through 15 incoming changesets (28 vs 63 instructions, in 4 conflict groups) 06-27 16:12:46.472 V/REALM_SYNC( 3481): Connection[2]: Session[2]: sync::create_table_with_primary_key(group, "class_SyncStringOnly", 15, "_id", 0); 06-27 16:12:46.472 V/REALM_SYNC( 3481): Connection[2]: Session[2]: sync::create_table_with_primary_key(group, "class_mongo_data", 15, "_id", 1); 06-27 16:12:46.472 V/REALM_SYNC( 3481): Connection[2]: Session[2]: sync::create_table_with_primary_key(group, "class_SyncStringOnly", 15, "_id", 0); 06-27 16:12:46.473 E/REALM_SYNC( 3481): Connection[2]: Session[2]: Failed to parse, or apply received changeset: ERROR: AddColumn 'class_SyncStringOnly.%3' which already exists
Root cause is unclear, but seems to be related to somehow running all the tests. So most likely a previous test is creating these instructions. SyncStringOnly is not part of the default schema, and is only used in SyncSessionTests and EncryptedSynchronizedRealmTests`, but running these locally before running this test has not proved a viable path or reproducing.