Fix JWT token discrepancy between diagnostic and bot API

[ishaileshpant]

🔧 Fix JWT Token Creation Discrepancy

Problem

The diagnostic endpoint shows JWT token creation as successful, but the bot API fails with JWT token errors. This indicates a discrepancy in how the private key is processed between the two endpoints.

Root Cause

• Diagnostic endpoint: Uses processed private key variable with escaped newlines handled
• Bot API: Uses raw environment variable in second createAppAuth call, causing inconsistency

Solution

• ✅ Fix private key consistency: Use processed privateKey variable in all createAppAuth calls
• ✅ Add diagnostic approach fallback: Try exact same approach as diagnostic endpoint if main approach fails
• ✅ Enhanced logging: Track token creation process and compare approaches
• ✅ Detailed debugging: Log token details for troubleshooting

Technical Changes

Fixed Private Key Consistency

// Before: Used raw environment variable
privateKey: process.env.GITHUB_APP_PRIVATE_KEY.replace(/\\n/g, '\n')

// After: Use processed privateKey variable
privateKey: privateKey

Added Diagnostic Approach Fallback

// If main approach fails, try diagnostic endpoint approach
try {
    const { createAppAuth: createAppAuthDiag } = await import('@octokit/auth-app');
    let diagPrivateKey = process.env.GITHUB_APP_PRIVATE_KEY;
    if (diagPrivateKey.includes('\\n')) {
        diagPrivateKey = diagPrivateKey.replace(/\\n/g, '\n');
    }
    // ... diagnostic approach
} catch (diagError) {
    // Both approaches failed
}

Enhanced Logging

• Token length and type logging
• Token prefix logging (first 20 chars)
• Detailed error comparison between approaches

Files Modified

• api/github/create-content-pr.js - Fixed JWT token creation consistency

Impact

• 🎯 Resolves JWT token creation discrepancy
• 🔄 Ensures consistent private key processing
• 🔍 Provides detailed debugging information
• 📊 Enables comparison between different approaches
• 🛠️ Fixes root cause of bot API failures

Testing

• Fixed private key consistency across all createAppAuth calls
• Added diagnostic approach fallback
• Enhanced logging for debugging
• No linting errors

Expected Results

The bot API should now work because:

1. Consistent private key processing matches diagnostic endpoint
2. Fallback to diagnostic approach if main approach fails
3. Detailed logging shows exactly what's happening

Next Steps

1. Test content submission to see if JWT token creation now works
2. Monitor logs to see which approach succeeds
3. Verify bot-only content submission works without fallbacks

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
prepguides-dev	Ready	Preview	Comment	Oct 13, 2025 3:18pm

[ishaileshpant]

/approve

[github-actions]

🚀 Admin-Approved and Auto-Merged!

This PR has been automatically merged to main after admin approval by @ishaileshpant.

✅ **Status**: Merged and deployed
🔗 **Commit**: `1dc5baa484619851a5f90d595e2906aad02bb5fe`
📅 **Merged at**: 2025-10-13T15:19:28.253Z
👤 **Approved by**: Admin/Maintainer/Owner

Thank you for your contribution! 🎉