-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor the SDK imports to prevent require cycles #29
Comments
Tried the example app in this project on on both iOS and android, this is still an issue.
In fact, after I connect my google account, nothing seems to happen afterwards. I'm still at the screen where the 3 buttons to login are found. |
Hi @lyqht, While the warning about require cycles will still appear, it does not cause any issues for now. I ran the demo app again to verify, and the flow works fine there. If you followed the steps in the README for the demo app, can you share any logs that appear in the Metro bundler or the Node server? |
hi @nkshah2, thank you for clarifying! I tested again, and it works now. It wasn't because of the require cycles problem - I just thought that the IP address given in the The command I used to get the IP address is from this StackOverflow thread, maybe we can consider adding an example to the README.
|
When using the SDK on iOS (tested with the example app in the repo) the bundler complains about require cycles in the code. One example of this is
fetch.ts
which importsrecipeImplementation.ts
which also importsfetch.ts
. While this is allowed and should not cause issues, react native warns that it might lead to uninitialised variables in future releases. We should refactor this to prevent cyclesThe text was updated successfully, but these errors were encountered: