-
Notifications
You must be signed in to change notification settings - Fork 663
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
Critical UX/DevX issues checklist #2518
Comments
not sure who checked 2488 checkbox, but let's mark only stuff that is in production (and verified at app level) as "fixed" for purposes of this tracker |
@vgrichina that is fair, but can you verify that it works now on betanet? |
@bowenwang1996 looks fine on betanet, except doesn't seem to be returning structured error:
|
@vgrichina is this an issue on nearcore side or near-api-js side? |
@bowenwang1996 on
|
@fckt Can you help us to set up the errors to be structured? |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
Looks like only the near-api-js one is still open. Closing this issue |
The text was updated successfully, but these errors were encountered: