Skip to main content
A quick check can resolve many temporary sign-in, loading, and save problems. If it does not, gather the details the team will need to reproduce the issue.

​
Try these steps

  1. Confirm your internet connection and reload the page once.
  2. Use the same sign-in method or wallet you normally use.
  3. Finish any pending wallet or identity prompt.
  4. Check required fields, links, dates, and permissions before saving again.
  5. Open dApp.ing in a current browser window without stale preview tabs.
  6. If one page fails, copy its production URL and note the action that caused it.

​
While troubleshooting

Wait for a save to finish before submitting again, and use the sign-in method connected to your existing profile. Keep seed phrases, private keys, passwords, session data, and identity documents private.

​
Report a reproducible issue

Include the page URL, approximate time, expected result, actual result, browser and device, and a screenshot with sensitive details removed. If dApp.ing saved the change but the public page looks old, open the exact public URL and refresh once. If the failure happens on an application, registration, wallet, or provider page, that service controls the next step. Record the production URL, time, browser, and safe error text before sending feedback.

​
Continue on dApp.ing

Report a bug or broken flow

Complete this task in the dApp.ing application.

Understand dApp.ing’s launch and responsibility boundaries

See what dApp.ing handles directly and when another service controls the next step.

Share useful product feedback

Share feedback the team can understand, reproduce, and act on.
Last modified on July 24, 2026