-
Notifications
You must be signed in to change notification settings - Fork 143
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
Crash on iOS 14 When Initializing SiweMessage Instance #185
Comments
osmanthustonx
changed the title
Crash on iOS 14 When Initializing SIWE Instance
Crash on iOS 14 When Initializing SiweMessage Instance
Nov 16, 2023
@osmanthustonx I'm running into the same issue! Did you manage to figure out what it was? |
@chrismin no idea🥲 |
Same |
Hello team? |
Any news, workarounds or updates on this topic? UA:
|
Having the same issue with Android |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The SIWE (Sign-In with Ethereum) library encounters a crash immediately upon initialization when running on iOS 14. This seems to be related to a syntax error in parser.js.
Steps to Reproduce
Expected Behavior
The SiweMessage instance should load without causing the app to crash.
Actual Behavior
The app crashes and the following error is displayed in the console:
(Unhandled Promise Rejection: Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
(Error: parser.js: initializeCallbacks(): syntax callback 'at' not a rule or udt name)
Possible Solution
N/A
Additional Information
Environment
Screenshots
Acknowledgements
I would like to express my gratitude to the development team for creating the SIWE library. Your work significantly contributes to the ecosystem, and I appreciate the effort put into making such tools available and maintained.
The text was updated successfully, but these errors were encountered: