[v3.7.0-alpha.2] CreatedAt must be of type 'date', got 'object'

[bimusiek]

Goals

Save model on node server with createdAt being new Date()

Expected Results

Model is saved

Actual Results

Got error

Error: LicenseRequestModel.createdAt must be of type 'date', got 'object' (Tue Mar 17 2020 20:03:14 GMT+0100 (Central European Standard Time))

Steps to Reproduce

Try to create new model on node server with new Date()

Code Sample

  static create<T>(this: RealmModelThis<T>, realm: Realm, props: any): T {
    return realm.create<T>(
      this.schema.name,
      {
        ...props,
        createdAt: new Date(),
        modifiedAt: new Date()
      },
      Realm.UpdateMode.All
    );
  }

Version of Realm and Tooling

• Realm JS SDK Version: v3.7.0-alpha.2
• Node or React Native: Node v13.3.0
• Client OS & Version: jest

[bimusiek]

Workaround for now was to use int and store date as a number. 😢

[kneth]

@bimusiek Could you post the schema?

[kneth]

@bimusiek We have release v5.0.0. Please try to upgrade.

[bimusiek]

I will check, thanks.

And do you know @kneth when are your team planning to release 4.0.0 beta with Node 13 support? 3.7.0 seems to work with newest node already.

[bimusiek]

@kneth With 5.0.0 there is the same issue.
Error: LicenseRequestModel.subscriptionExpiresAt must be of type 'date?', got 'object' (Thu Mar 12 2020 11:48:52 GMT+0100 (Central European Standard Time))

Schema:

  public static schema = {
    ...BaseModel.schema,
    name: 'LicenseRequestModel',
    primaryKey: 'licenseId',
    properties: {
      ...BaseModel.schema.properties,
      licenseId: 'string',
      token: { type: 'string', default: '' },
      email: { type: 'string', default: '' },
      status: { type: 'int', default: LicenseRequestStatus.INITIALIZED },
      type: { type: 'int', default: LicenseRequestType.WEB },
      hasSubscription: { type: 'bool', default: false },
      subscriptionExpiresAt: 'date?'
    }
  };

export abstract class BaseModel {
  public static schema = {
    properties: {
      createdAt: 'int',
      modifiedAt: 'int'
    }
  };

[kneth]

@bimusiek Thank you for the update. Could you try subscriptionExpiresAt: { type: 'date', optional: true} instead. If that works, we have a bug in the schema parser, and if it does, the bug is in the object creation code.

[bimusiek]

Unfortunately, the same issue.

[xmedeko]

We use JS, Realm 5 and date, date? are ok. E.g.

const schema = [
    {
        name: "Something",
        properties: {
            data: "string",
            createdAt: "date",
            changedAt: "date?"
        }
    }];
Realm.open(schema);

Then create, update etc. is OK.

[kneth]

It looks like the issue is how we interact with classes rather than a Date issue. @bimusiek Can you try to write your schema as suggested in #2755 (comment)

[bimusiek]

@kneth The schema I pass to Realm constructor is

  const realmConfig = user.createConfiguration({
    schema,
    schemaVersion,
    sync: {
      url: `~/app`,
      fullSynchronization: true
    }
  });
  const realm = new Realm(realmConfig);

where schema is:

export const schema = [
  ConfigRealmModel.schema,
  CollectionModel.schema,
  CollectionItemModel.schema,
  ImporterAuthenticationModel.schema,
  TransferModel.schema,
  TransferCollectionModel.schema,
  TransferCollectionItemModel.schema,
  LicenseRequestModel.schema
];
export const schemaVersion = 1;

So as I understand, it is done in the same manner by passing JS object directly.
Also, it worked with 4.0.0 alpha.

I forgot to mention that I use in memory realm for Jest tests, maybe there is an issue?

[voidrender]

I forgot to mention that I use in memory realm for Jest tests, maybe there is an issue?

I'm also running into this issue only while using an in-memory Realm for Jest tests.

[mtford90]

Facing this issue myself with jest tests using inMemory Realm.

Works fine on 3.6.5

[d3v2a]

I'm also running into this issue only in jest test (in-memory or not)

the same code directly in node work fine

to get it working in jest:

new Date().toISOString();