# Schema mismatch, expected Pointer

**URL:** <https://community.parseplatform.org/t/schema-mismatch-expected-pointer/2573>\
**Category:** Uncategorized\
**Created:** [April 4, 2022, 6:22pm UTC](https://community.parseplatform.org/t/schema-mismatch-expected-pointer/2573 "2022-04-04T18:22:07Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![davimacedo](https://community.parseplatform.org/user_avatar/community.parseplatform.org/davimacedo/32/316_2.png) [@davimacedo](https://community.parseplatform.org/u/davimacedo)\
**Post date:** [April 5, 2022, 12:21am UTC](https://community.parseplatform.org/t/schema-mismatch-expected-pointer/2573/4 "2022-04-05T00:21:17Z")

</div>

Instead of:

```auto
return await user.signUp(null, { useMasterKey: true });

```

try:

```auto
await user.save(null, { useMasterKey: true });
return user;

```

Talking about jest, I’d need to better understand your setup. It might be related to the fact that you are probably running a Parse Server instance in the same process. Parse Server also instantiates the SDK. You can find some inspiration here: [parse-blockchain/packages/integration at master · parse-community/parse-blockchain · GitHub](https://github.com/parse-community/parse-blockchain/tree/master/packages/integration)

---

_[View the full topic](https://community.parseplatform.org/t/schema-mismatch-expected-pointer/2573)._