Open manufunk opened 4 months ago
I believe this has been fixed via https://github.com/parse-community/Parse-SDK-JS/pull/2109
Can you try the latest alpha release?
I ran into the same issue, and was only able to resolve it by downgrading to parse
4.2.0 as noted by this stack overflow answer. My app was still using 4.x anyways (I know I need to upgrade, but I also need to upgrade parse-server
and mongodb
before I can do that). This seems to be an incompatibility with Expo SDK 50+.
New Issue Checklist
Issue Description
If using react native and expo, I receive an error if I do something like
const parseQuery = new Parse.Query("Config");
. This happened after upgrading the parse library. It seems that 4.x is affected and also the 5.0.0Steps to reproduce
I created a sample project that will end up in an error. Just use
yarn install
and thenyarn run start
. I tested on the android emulator via expo app. However same happens on ios.Actual Outcome
The following error is thrown:
Expected Outcome
No such error. The sample shows that if switched back to 3.5.1, the error does not appear but it is very old.
Client
Sample for reproduction
example.zip