PEX.validateDefinition gives different results based on whether it is ran in Node.JS or React Native

[TimoGlastra]

• I'm submitting a ...
  [x] bug report

• Summary

Calling PEX.validateDefinition gives different results based on whether it is ran in Node.JS or React Native.

When calling validateDefinition on the following definition:

{
   "id":"022c2664-68cc-45cc-b291-789ce8b599eb",
   "purpose":"We want to know your name and e-mail address (will not be stored)",
   "input_descriptors":[
      {
         "id":"c2834d0e-3c95-4721-b21a-40e3d7ea2549",
         "name":"DBC Conference 2023 Attendee",
         "purpose":"To access this portal your DBC Conference 2023 attendance proof is required.",
         "schema":[
            {
               "uri":"DBCConferenceAttendee"
            }
         ],
         "constraints":{
            "fields":[
               {
                  "path":[
                     "$.credentialSubject.event.name",
                     "$.vc.credentialSubject.event.name"
                  ],
                  "filter":{
                     "type":"string",
                     "pattern":"DBC Conference 2023"
                  }
               }
            ]
         }
      }
   ]
}

The result in Node.JS (v18) for me is:

[ Checked { tag: 'root', status: 'info', message: 'ok' } ]

While in React Native I get:

[
   {
      "message":"presentation_definition should be as per json schema.",
      "status":"error",
      "tag":"root.presentation_definition"
   },
   {
      "message":"field object \"filter\" property must be valid json schema",
      "status":"error",
      "tag":"presentation_definition.input_descriptor[0].constraints.fields[0]"
   }
]

Not really an idea why this is happening. Bot environments are using 2.0.1 of PEX

• Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

[nklomp]

@TimoGlastra Is this with the Hermes engine in RN?

This is a known issue to us and the reason why we switched to JCS. We should also be able to solve it, as we did that in the SIOP lib as well. @sksadjad will be picking this up shortly

[nklomp]

I got from Slack that indeed it is Hermes.

@TimoGlastra Could you test with version 2.0.2-unstable.3, it should have fixed this issue (at least in our wallet). It also brings some more performance, as we moved AJV compilation to the build phase instead of doing it at runtime on the phone.

[nklomp]

Please reopen in case it is not fixed. Should be resolved from version 2.0.3-unstable.3. A 2.1 will be release shortly