I am new to back4app and parse. I am trying to learn to integrate it in my app.
React Native ver: 0.64 Platform: Android
But I am having error on the initialization using Parse SDK for react native. I just followed the steps on the documentation and I get this error:
Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js - > node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseACL.js Require cycles are allowed, but can result in uninitialized values. Consider refactoringto remove the need for a cycle. TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap, "../../../react-native/Libraries/vendor/emitter/EventEmitter").prototype.addListener') ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
I also tried the Parse React Native initialization and I get the same error
How do I fix this?
If you use React Native version 0.63.4, do you also face this issue?
Could you please also share the code that you are using in order to initialize the SDK?
@charles you are right it is not working well with the new RN ver .64, I downgraded back to RN 0.63.4 and it is working now.
Though the rquire cycle warning message still appears the error message is gone. Is the warning message something to worry about?
@davimacedo I am using the todo example code in the documentation for testing purposes only, I have not implement it yet on my actual app.
@destructivetypeunit02 good to hear that from you!
Since it's just a warning, if everything works as expected, you can change the priority of updating it, but it's important to do so.
You mentioned that you are using our todo example code, I'll forward it to our team to take a look at it.
@charles actually the warning message appears the moment I initialize with parse neither with this
@destructivetypeunit02 thanks for these details! We will investigate it further and solve that.
In case of any uncommon behaviors you find regarding public datasets, do not hesitate to open an issue.
For any assistance that you might need, you can reach out here: https://www.back4app.com/support