Skip to content

TROUBLESHOOTING.adoc

Latest commit

 

History

History
193 lines (122 loc) · 3.71 KB

TROUBLESHOOTING.adoc

File metadata and controls

193 lines (122 loc) · 3.71 KB

Zaplie for DevOps - Troubleshooting Guide

Table of Contents

Common Issues

"Zap" button doesn’t appear

Symptoms: The "Zap" option is missing from work item context menu.

Possible causes:

  1. Extension not installed

  2. Extension not shared with your organization

  3. Browser cache

Solutions:

  1. Verify extension is installed: Organization settings → Extensions

  2. Clear browser cache and refresh

  3. Check extension scope requirements

"No assignee" error

Symptoms: Dialog shows "Work item has no assignee".

Cause: The selected work item doesn’t have an assignee.

Solution: Assign the work item to a user before zapping.

Lightning address not found

Symptoms: Dialog shows "This user hasn’t configured a Lightning address yet."

Cause: The assignee hasn’t set up their Lightning address.

Solution: Ask the assignee to configure their address:

  1. Organization settings → Zaplie Settings

  2. Enter Lightning address

  3. Click Save

Invoice fetch failed

Symptoms: Error message "Failed to fetch invoice" or "LNURL endpoint returned XXX".

Possible causes:

  1. Invalid Lightning address

  2. LNURL server is down

  3. CORS restrictions

Solutions:

  1. Verify the Lightning address is correct (format: name@domain.com)

  2. Test the address at https://lightningaddress.com

  3. Check if the wallet provider’s servers are operational

QR code won’t scan

Symptoms: Lightning wallet can’t read the QR code.

Solutions:

  1. Ensure adequate screen brightness

  2. Try increasing device camera resolution

  3. Copy invoice manually using the copy button

  4. Use "Open in Wallet" button if on mobile

Comment not posted

Symptoms: Zap confirmed but no comment appears on work item.

Possible causes:

  1. Insufficient permissions

  2. API rate limiting

Solutions:

  1. Verify you have permission to comment on work items

  2. Check browser console for API errors

  3. Wait a moment and refresh the work item

Authentication Issues

Graph API errors

Symptoms: "Failed to get Lightning Address" or similar Graph errors.

Cause: Token or permission issues.

Solutions:

  1. Sign out and sign back in to Azure DevOps

  2. Clear browser cookies for dev.azure.com

  3. Verify extension has required scopes (vso.graph)

Token refresh issues

Symptoms: Actions fail after extended session.

Solution: Refresh the page to get new tokens.

Build Issues

VSIX creation fails

Symptoms: bun run package-dev fails.

Solutions:

# Ensure tfx-cli is installed
npm install -g tfx-cli

# Clean and rebuild
rm -rf dist *.vsix
bun install
bun run package-dev

TypeScript errors

Solutions:

# Check TypeScript
bun run typecheck

# Common fix: reinstall dependencies
rm -rf node_modules
bun install

Missing VSS SDK types

Solution: Ensure vss-web-extension-sdk is installed:

bun add -D vss-web-extension-sdk

Debugging

Browser Console

Open browser developer tools (F12) and check:

  1. Console for JavaScript errors

  2. Network tab for failed API calls

  3. Look for [ZapDialog] or [Zaplie] prefixed logs

Enable Verbose Logging

Add to browser console:

localStorage.setItem('zaplie-debug', 'true');

Then refresh the page.

Test Lightning Address Manually

# Test LNURL-pay endpoint
curl https://domain.com/.well-known/lnurlp/username

Getting Help

Report Issues

Include:

  • Browser and version

  • Azure DevOps organization type (cloud/server)

  • Error messages from console

  • Steps to reproduce

Related Documentation