Identifier is set to zero when entity is fetched from database

[JulienLHPro]

Bug description Identifier is set to zero when entity is fetched from database

Basic info

• ObjectBox 2.1.0
• Reproducibility: always
• Device: Android simulator
• OS: API 31

To Reproduce No idea, but it does not happen on all entities

Expected behavior When fetched from database, entity identifier should not be zero

Code

• Entity:

@Entity()
class ItemEntry {
  @Id()
  int internalID = 0;

  String clientID;
}

• Insertion:

store.box<ItemEntry>().put(itemEntry, mode: PutMode.put)

After insertion, itemEntry.internalID is 1

• Later:

ItemEntry? itemEntry = store
        .box<ItemEntry>()
        .query(generated.ItemEntry_.clientID.equals(clientID))
        .build()
        .findFirst();

itemEntry is not null and has all correct values, except for itemEntry.internalID which is 0

Logs, stack traces Because of all relations I skipped here, I end up with this error: "Bad state: Can't store relation info for the target object with zero ID"

Additional context The main insertion is done in a Transaction, but the problem is the same without it.

[JulienLHPro]

Additional note: on Admin page, internalID correctly starts at 1

[greenrobot-team]

Thanks for reporting! I don't see anything obvious. Can you provide a working unit test or minimal example project that reproduces this?

[JulienLHPro]

I fixed my issue but one might find interesting the fact that you can't set a relationship in the constructor: this.macroCategoryEntry.target = although you would get no error apart from getting a zero internalID when fetching that entity later

[greenrobot-team]

Good to hear. However, from the top of my head there should be nothing preventing you from setting a ToOne target in the constructor?