Osmyntv1.3.8
Common Issues
This guide covers the most frequently encountered problems with Osmynt and their solutions.
Installation Issues
Extension Not Appearing
Symptoms:
- Osmynt icon not visible in Activity Bar
- Extension not listed in Extensions view
- Commands not available in Command Palette
Solutions:
- Reload VS Code: Close and reopen VS Code
- Check VS Code version: Ensure you're running VS Code 1.94.0 or later
- Reinstall extension: Uninstall and reinstall Osmynt
- Check installation: Go to Extensions view and verify Osmynt is installed and enabled
Permission Issues
Symptoms:
- "Permission denied" errors during installation
- Extension fails to load
- VS Code crashes when opening Osmynt
Solutions:
- Restart VS Code as Administrator (Windows) or with
sudo(macOS/Linux) - Check VS Code permissions: Ensure VS Code has necessary permissions
- Update VS Code: Ensure you're running the latest version
- Check system permissions: Ensure your user account has necessary permissions
Authentication Issues
"Authentication Failed" Error
Symptoms:
- Browser doesn't open for authentication
- "Authentication failed" message appears
- Cannot sign in to GitHub
Common causes:
- Network connectivity issues
- GitHub service temporarily unavailable
- Browser popup blocked
Solutions:
- Check internet connection
- Allow popups for VS Code in your browser
- Try again - GitHub services are usually restored quickly
- Restart VS Code and try again
"Permission Denied" Error
Symptoms:
- "Permission denied" when trying to authenticate
- Cannot access GitHub account
- Authentication process fails
Common causes:
- GitHub account restrictions
- Organization policies blocking third-party apps
- Two-factor authentication issues
Solutions:
- Check GitHub settings: Go to GitHub → Settings → Applications
- Check organization policies: Contact your GitHub organization admin
- Use personal account: Try with a personal GitHub account first
- Disable 2FA temporarily: If possible, disable 2FA temporarily
"Session Expired" Error
Symptoms:
- "Session expired" message appears
- Cannot access teams or shared code
- Need to re-authenticate frequently
Common causes:
- GitHub token expired
- Long period of inactivity
- GitHub security policy changes
Solutions:
- Re-authenticate: Run
Osmynt: Loginagain - Check GitHub security: Review your GitHub security settings
- Clear cache: Run
Osmynt: Clear Local Cacheif issues persist - Check token permissions: Ensure GitHub token has necessary permissions
Team Issues
"Failed to Join Team" Error
Symptoms:
- Cannot join team with invitation token
- "Failed to join team" error message
- Team invitation not working
Common causes:
- Invalid or expired invitation token
- Network connectivity issues
- Team no longer exists
Solutions:
- Check the token: Ensure it's copied correctly
- Get a new invitation: Ask team owner for a fresh token
- Check network: Ensure you have internet connectivity
- Try again: Sometimes temporary network issues cause failures
"Team Not Found" Error
Symptoms:
- "Team not found" error message
- Cannot access team after joining
- Team disappears from panel
Common causes:
- Team was deleted
- You were removed from the team
- Token is for a different team
Solutions:
- Contact team owner: Ask for a new invitation
- Check team status: Verify the team still exists
- Get fresh token: Request a new invitation token
- Re-authenticate: Run
Osmynt: Loginagain
Team Members Not Appearing
Symptoms:
- Team members don't appear in panel
- Cannot see other team members
- Team appears empty
Common causes:
- Team members haven't joined yet
- Network sync issues
- Extension cache problems
Solutions:
- Refresh the panel: Run
Osmynt: Refresh - Check member status: Ensure members have joined
- Clear cache: Run
Osmynt: Clear Local Cacheif needed - Wait for sync: Sometimes it takes a few minutes
Code Sharing Issues
"No Code Selected" Error
Symptoms:
- "No code selected" error when trying to share
- Cannot share code snippets
- Share button not working
Solutions:
- Select code first: Select some code in your editor
- Check selection: Ensure code is properly selected
- Try different selection: Select code using different methods
- Restart VS Code: If issues persist, restart VS Code
"Share Failed" Error
Symptoms:
- "Share failed" error message
- Cannot share code with team
- Sharing process fails
Common causes:
- Network connectivity issues
- Authentication problems
- Team access issues
Solutions:
- Check internet connection
- Run
Osmynt: Refreshto sync - Try sharing again
- Check team access: Ensure you're a member of the team
Code Not Appearing
Symptoms:
- Shared code doesn't appear in panel
- Cannot see shared code from team members
- Code sharing not working
Solutions:
- Run
Osmynt: Refreshto sync - Check if you're in the right team
- Verify the share was completed successfully
- Check team member status: Ensure team members are active
Device Issues
Device Not Syncing
Symptoms:
- Changes not appearing on other devices
- Device not receiving updates
- Multi-device sync not working
Common causes:
- Network connectivity issues
- Authentication problems
- Extension cache issues
Solutions:
- Check internet connection: Ensure stable connectivity
- Re-authenticate: Run
Osmynt: Loginagain - Refresh sync: Run
Osmynt: Refresh - Clear cache: Run
Osmynt: Clear Local Cacheif needed
Device Not Appearing
Symptoms:
- Device doesn't appear in device list
- Cannot see device in panel
- Multi-device setup not working
Common causes:
- Device not properly authenticated
- Network sync issues
- Extension installation problems
Solutions:
- Verify installation: Ensure Osmynt is properly installed
- Check authentication: Ensure you're logged in
- Wait for sync: Sometimes it takes a few minutes
- Restart VS Code: Restart VS Code and try again
Performance Issues
Slow Performance
Symptoms:
- Osmynt panel loads slowly
- Code sharing takes a long time
- VS Code becomes unresponsive
Common causes:
- Large code blocks
- Network latency
- Extension conflicts
Solutions:
- Reduce code size: Keep shared code blocks smaller
- Check network speed: Ensure fast internet connection
- Disable other extensions: Temporarily disable other extensions
- Restart VS Code: Restart VS Code to clear memory
High Memory Usage
Symptoms:
- VS Code uses excessive memory
- System becomes slow
- Out of memory errors
Solutions:
- Clear cache: Run
Osmynt: Clear Local Cache - Restart VS Code: Restart VS Code to clear memory
- Check for memory leaks: Monitor memory usage over time
- Update extension: Ensure you're running the latest version
Network Issues
Connection Problems
Symptoms:
- Cannot connect to Osmynt servers
- Network errors appear
- Sync fails repeatedly
Common causes:
- Firewall blocking connections
- Corporate network restrictions
- DNS resolution issues
Solutions:
- Check firewall settings: Ensure VS Code can access the internet
- Check corporate policies: Contact your IT department
- Try different network: Test with different internet connection
- Check DNS settings: Ensure DNS is working correctly
Corporate Network Issues
Symptoms:
- Cannot access Osmynt from corporate network
- Authentication fails
- Network timeouts
Solutions:
- Contact IT department: Ask about network restrictions
- Use VPN: Try using VPN if available
- Check proxy settings: Configure proxy if needed
- Use personal network: Test with personal internet connection
Getting Help
Before Contacting Support
- Check this guide: Look for your specific issue
- Try basic solutions: Restart VS Code, clear cache, re-authenticate
- Check system requirements: Ensure your system meets requirements
- Update everything: Ensure VS Code and Osmynt are updated
Contacting Support
When contacting support, include:
- Detailed description of the problem
- Steps to reproduce the issue
- System information (OS, VS Code version, etc.)
- Error messages (if any)
- What you've tried to fix the issue
Support Channels
- 📧 Email: support@osmynt.dev
- 🐛 GitHub Issues: Report issues
Prevention Tips
Regular Maintenance
- Keep VS Code updated: Ensure you're running the latest version
- Keep Osmynt updated: Update the extension regularly
- Clear cache periodically: Run
Osmynt: Clear Local Cacheoccasionally - Monitor performance: Watch for performance issues
Best Practices
- Use stable internet: Avoid unstable network connections
- Keep code blocks small: Avoid sharing very large code blocks
- Regular team cleanup: Remove inactive team members
- Monitor device usage: Remove unused devices
Next Steps
If you're still experiencing issues:
- Check device problems - Multi-device specific issues
- Check connection issues - Network and sync problems
- Check performance issues - Performance optimization
- Contact support - Get help from our team