-
Notifications
You must be signed in to change notification settings - Fork 586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CERT_HAS_EXPIRED #4619
Comments
Hey Saalim, apologies for that - we must have overlooked renewing the certificate. The SRE team is looking into this, but it may be a couple of hours before the issue is resolved. |
Thanks for your prompt response. I just tried to install right now, it is now throwing a different error.
|
Could this be related to #4618? There is a line that says
|
yes @thespacemanatee |
Download url: https://static.realm.io/downloads/sync/realm-sync-node-cocoa-4.9.5.tar.gz Update: Resolved |
Hey folks, the certificate problem should be resolved now. Apologies for the disruption. |
@nirinchev Hello! I know it's a Sunday night 6 months later but I'm experiencing this issue again. I made an EAS dev build and everything worked fine, then other builds started failing. |
How frequently does the bug occur?Roughly every six months. |
I opened a new issue for this (#5228) and just now noticed there were updates here too. Glad to know I'm not crazy. Although annoying that I have spent the last two hours troubleshooting something that is as simple as a cert renewal 😞 I really hope that the Realm team can put together an automated process that makes sure this doesn't happen again because it appears over the last couple years this has happened several times :( |
Very sorry about this - it shouldn't happen of course. We are looking into this. |
FYI for future I posted a one liner to use with PowerShell (Windows) that should work with an expired certificate as a temporary workaround if needed: #5228 (comment) |
How frequently does the bug occur?
All the time
Description
Hi, when I try to install all packages by "npm i" I am seeing the follwoing error. It was not happening before.
Stacktrace & log output
Can you reproduce the bug?
Yes, always
Reproduction Steps
No response
Version
"realm": "^3.6.0"
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
MacOS
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: