responsively-app icon indicating copy to clipboard operation
responsively-app copied to clipboard

Can't install Chrome extension anymore (Manifest V3)

Open ShinobiWPS opened this issue 8 months ago โ€ข 3 comments

๐Ÿž bug report

โœ๏ธ Description

If you go to the Chrome extension page, you can't get the extension anymore, most probably because it's not updated with the new Manifest V3.

๐Ÿ•ต๐Ÿผโ€โ™‚๏ธ Is this a regression?

yes

๐Ÿ”ฌ Minimal Reproduction

  1. Use Chrome Browser (from Edge, you get a warning but you are still able to install it)
  2. got to chrome extension page
  3. the plugin is not available anymore

๐ŸŒ Your Environment

Chrome browser

๐Ÿ”ฅ Exception or Error or Screenshot

Image

ShinobiWPS avatar May 02 '25 08:05 ShinobiWPS

๐Ÿšจ Urgent Attention Needed: Manifest Compliance and Security Concerns

โ€œSecurity isn't optional โ€“ it's fundamental.โ€


โ— Problem Statement

The current version of this project appears to not comply with the latest Google security standards, particularly concerning the Chrome Manifest updates. This issue stems from the use of deprecated manifests, which Google has clearly marked for review and updating.

Unfortunately, it seems this concern has been overlooked or ignored, despite likely communications and reminders from Google.


โš ๏ธ Consequences of Inaction

  • โŒ Loss of Trust: Users lose confidence in the platform when they encounter warnings or blocked extensions/apps due to security violations.
  • ๐Ÿ“‰ Reduced Accessibility: With Chrome revoking support, users are also less likely to trust or use the product on other platforms.
  • ๐Ÿงจ Brand Damage: Failing to meet modern security standards can severely impact the reputation and reliability of the project.
  • ๐Ÿ“ช Missed Notifications: Ignoring Google's mails and alerts further implies a lack of active maintenance, which is a red flag for users and contributors alike.

โœ… Suggested Action Plan

๐Ÿ”„ 1. Update the Manifest

Ensure the project complies with the latest Manifest v3 requirements. This includes:

  • Upgrading permissions and background script handling.
  • Ensuring all APIs used are still supported.
  • Fixing any deprecated features or flags.

๐Ÿ•ต๏ธ 2. Audit Security Practices

Perform a security audit:

๐Ÿ“ฌ 3. Monitor and Respond to Google Alerts

Set up a watch mechanism for:

  • Emails from Google Developer accounts.
  • Official documentation updates.
  • Community discussions on extension compliance.

๐Ÿค Why This Matters

Your project has a strong following and user base. Neglecting fundamental updates like these undermines years of hard work and trust. It's not just a technical issue โ€” it's a credibility issue.

Users need to feel safe, contributors want to see responsiveness, and platforms demand compliance.

Letโ€™s make sure this project keeps shining ๐ŸŒŸ โ€” not fading away due to preventable missteps.


๐Ÿ“Œ Conclusion

Act now.
Letโ€™s fix the manifest. Secure the platform.
Regain trust โ€” and grow stronger than before.

Security is not a one-time feature โ€” itโ€™s a continuous commitment.


๐Ÿ›  Authored by a concerned contributor who cares deeply about the projectโ€™s future and its community.

the above comment its definitely made by AI

ShinobiWPS avatar Jun 11 '25 11:06 ShinobiWPS

I wanted to try Responsively to see how it works and if i can add it to my work flow but I noticed that I can't install chrome extensions. In chrome itself i have been using automa to hold dummy login credentials so i don't need to manually copy and paste each dummy accounts. Unless there are other extensions out there for this kind of task. I think this could be worked around by using the responsively helper extension while keeping automa in my actual chrome browser but responsively help can't be installed in responsively.

ysk3a avatar Nov 22 '25 22:11 ysk3a