EPERM: operation not permitted, open '....node_modules\win-ca\pem\roots.pem'

• SKD version - @sentry/electron@v1.1.0
• Electron version - electron@v7.1.5
• Platform - Windows Store

Description

Since we upgraded this package from v1.0.0 to v1.1.0 we see a lot of these errors for our Windows Store users:

EPERM: operation not permitted, open 'C:\Program Files\WindowsApps\<APP_NAME>.27241E05630EA_2.11.3.0_x86__kn85bz84x7te4\app\resources\app.asar.unpacked\node_modules\win-ca\pem\roots.pem'

I noticed in the changelog that you introduced this win-ca package in v1.1.0. Looks like this issue might be related?

Is downgrading to v1.0.0 the best solution for now? I couldn’t find any open issues, hence why I opened this one.

[timfish]

The virtualisation could certainly be the issue. win-ca will apparently attempt a few paths and the virtualisation can give the appearance of writing success but as files don’t persist this will then cause issues. I’ve opened a PR (#206) that makes win-ca use the sentry cache path which will hopefully fix this as we know it’s writable. I’ve also made it so that any errors that occur while calling win-ca are now ignored as this failure will not impact the vast majority of users.

electron-fetch was completely broken for electron@7 for a couple of months and it has also broken functionality in sentry-electron before. It did get fixed to work for electron@7, but there are many unresolved issues and while these issues are outstanding, it doesn’t seem like a great idea to continue to rely on it as a dependency.

[HazAT]

1.2.0 is out now