Wasil

Let’s get you unstuck.

Start with the documentation, then email wasil@aramb.dev with enough context for us to reproduce the problem.

Email wasil@aramb.devRead the docs

Security rule: Never include a Vercel token, password, session token, environment value, or private deployment data in an email.

Before you write

  1. Confirm that your Vercel token is active.
  2. Check that it has the permissions listed in the documentation.
  3. Try reconnecting or switching connection modes.
  4. Check whether the same project loads in the Vercel dashboard.

What to include

Useful, non-sensitive details help us investigate quickly:

  • Wasil app version and iOS version.
  • iPhone model.
  • Connection mode: Default or Private.
  • The screen and action where the issue occurred.
  • A timestamp and a redacted error message.
  • The affected project or deployment name only if it is safe to share.

Common issues

“Invalid token” Recreate or re-enable the Vercel token, check its permissions, and reconnect.
Projects are empty Confirm the token can access the relevant team or workspace, then pull to refresh.
Default Mode is unavailable Try again after a short wait or use Private Mode for direct Vercel access.
Environment coverage is incomplete Wasil reports key presence by target; it does not inspect secret values or validate their contents.

Privacy and deletion

For a privacy question or a request to remove a stored Wasil connection, email wasil@aramb.dev without including credentials. See the Privacy Policy for the current data-handling and deletion description.

Responsible disclosure

If you believe you found a security issue, do not post sensitive details publicly. Email wasil@aramb.dev and describe the issue without sharing secrets.