Update background script to sync user integration settings on login

[bluant]

Fix Integrations After Reopeining Browser

Summary

This is a small fix for integrations not being avaialble after the browser is closed and opened again. When the user is already logged in, we now run the existing integration setup during browser startup as well.

Context

The extension can still be logged in after restart, but the integration scripts are not always registred again. In that case supported pages can load without the Clockify integration UI until something else causes the setup flow to run.

What Changed

• Added 3 lines inside runtime.onStartup for logged-in users:
  • setIntegrationSettingsForCurrentUser()
  • unregisterAllIntegrations()
  • registerEnabledIntegrations()

Expected Behavior

• Enabled integrations should be available after a browser restart.
• Existing enabled/disabled integration settings and custom URLs should still be used.
• Existing login and logout behavior should remain the same.

User Impact

This should mostly be invisible to users. The main difference is that integrations should show up again after browser reopen, without users needing to refresh around or re-open the extension to get things working.

Files Changed

• src/contentScripts/background.js

Testing

Commands run:

• npm test - not available; this project currently has a placeholder test script that exits with Error: no test specified.
• npm run compile.dev.chrome.nowatch - passed.
• npm run compile.dev.firefox.nowatch - passed.

Manual validation that is still worth doing:

• Log in and confirm enabled integrations are registered.
• Restart the browser and confirm integrations are still active for the logged-in user.
• Open a supported integration page after restart and confirm the Clockify integration UI appears.

Risk

Low. The change is only in the startup listener and reuses the same setup calls that already exist in the login/install path. A quick manul pass is still recommended because this depends on browser lifecycle behaviour.

[milosfromcake]

Hello @bluant.

Thanks for your efforts to improve our project.

In the coming days, we will review and test your changes, after which we will inform you of the next steps.

All the best. 🙌

[milosfromcake]

Hello, @bluant.

Can you provide us with the exact steps to reproduce the problem you solved with these changes?

Our QA team is currently unable to reproduce this issue.

Thanks in advance.

[bluant]

Hey, @milosfromcake.

Yeah sorry I should've included them in the pr originally.

Basically:
macOS version: 26.5, build 25F71
Chrome version: 148.0.7778.181
Clockify extension version: 2.11.48 (installed via chrome extension store)

Steps to reproduce:

1. Open chrome and login into the clockify extension.
2. Go to integrations and setup custom integration with redmine

3) Refresh the redmine app and everything works as expected, every ticket has clockify start timer on it. Great!

Then from whatever reason, chrome gets killed completely or pc gets restarted.

• The startTime isn't visible anymore on tickets in redmine, but the clockify integrations still show that the integration is added there.
• I have to delete and add the integration again for the startTimer to be visible in redmine again.

Side note - "Soft closing" chrome on macos keeps the timer shown correctly and you can close chrome as much times as you want and it'll always be shown. But restarting pc or killing chrome completely requires reapplying integrations.