Google Drive sign-in fails on Microsoft Edge

Bug Description

The Google Drive sign-in functionality does not work on Microsoft Edge. When attempting to sign in to save recordings to Google Drive, the authentication fails with an error.

Expected Behavior

Users should be able to:

1. Click on "Save to Google Drive" option
2. Complete the Google OAuth authentication flow
3. Successfully upload their recordings to Google Drive

Actual Behavior

When attempting to sign in on Microsoft Edge:

1. The sign-in process fails immediately
2. The following error appears in the console:

   Error signing in: This API is not supported on Microsoft Edge. For more details, see extensions API documentation
   

3. Users cannot save their recordings to Google Drive

Error Details

Console Error Messages:

Error signing in: This API is not supported on Microsoft Edge. For more details, see extensions API documentation
Error uploading to Google Drive: Sign-in failed
Uncaught (in promise) Error: Sign-in failed

Additional Error When Attempting Sign-in:

Error 400: redirect_uri_mismatch
Acceso bloqueado: la solicitud de esta aplicación no es válida

Root Cause

The extension uses chrome.identity.getAuthToken() API which is not supported in Microsoft Edge. According to Microsoft's documentation, this Chrome-specific API is not available in Edge extensions.

Steps to Reproduce

1. Install Screenity extension in Microsoft Edge
2. Start a recording
3. After recording, attempt to save to Google Drive
4. Click on the Google Drive sign-in button
5. Observe the error in the browser console

Environment

• Browser: Microsoft Edge (Version 131.0.2903.40 or any recent version)
• Extension Version: 3.1.13
• Operating System: Windows 10/11
• Extension Load Method: Chrome Web Store / Local development

Impact

• Users on Microsoft Edge cannot use the Google Drive integration
• This affects a significant user base as Edge has substantial market share
• Users must download videos locally instead of sharing via Google Drive links

Possible Solution

Replace chrome.identity.getAuthToken() with chrome.identity.launchWebAuthFlow() for Edge browsers, implementing a manual OAuth2 flow.

Related Information

• Microsoft Edge Extensions API Documentation: https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/
• Similar issues in other extensions migrating to Edge

Checklist

• I have searched for similar issues
• I have tested on the latest version of the extension
• I have provided clear reproduction steps
• I have included relevant error messages
• This issue only occurs on Microsoft Edge (works fine on Chrome)