-
Notifications
You must be signed in to change notification settings - Fork 42
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
React Native got error: "Browser history needs a DOM" #11
Comments
I also hear there are some needed crypto functions that will not work with RN. |
@jcalfee This error may be caused by using "createBrowserHistory", use "createMemoryHistory" can fix it. |
The code your pointing to is in browser.js .. I don't have a RN environment setup now, I will get some feedback on this and see what I can do though. I suspect there are going to be many changes for RN. |
The best thing for you may be to fork this repo and make the change yourself (until I have done enough research to start changing things). You'll probably uncover more issues .. Please also make sure that this is the library you need. This is designed to derive and cache keys but also needs a password manager to store a "root" key. This library does not have secure or password protected storage. It does however figure out permission hierarchies and is configurable enough to only store keys you feel are safe to store. |
Thank you for your reply. |
when import eosjs-keygen, i got the error: "Browser history needs a DOM"
Environment
The text was updated successfully, but these errors were encountered: