-
Notifications
You must be signed in to change notification settings - Fork 270
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
Debugging Expo app in VSCode causes a certificate expired error. #1679
Comments
I was coming here to report the same problem |
I understand that there is some let's encrypt certificate expiring microsoft/vscode#134244
|
Hi @BlueDevil2k6 @superandrew and thanks for reporting. Under the hood the extension uses |
thank you @RedMickey. I noticed there is no open issues on expo-cli about this. Is this because there is nothing that can be done on expo-cli side? |
@superandrew It seems that this issue is more Electron specific. It's fixed in the recent version of Electron, but could persists in previous versions. So, we opened a question about updating Let’s Encrypt root certificate in Expo. |
@superandrew @BlueDevil2k6 The issue is fixed in the latest version of VS Code Insiders. Could you please try it out to check if it works for you? |
Thanks for following up on this. I've confirmed that this issue no longer appears in VS Code Insiders build 1.61.0-insider. Version: 1.61.0-insider (Universal) What's the ETA on 1.61 making it as the official release? |
@BlueDevil2k6 According to this plan, the approximate release date is October 6, 2021. So, I think VS Code v1.61 stable will be released soon (maybe within this or next week). |
@BlueDevil2k6 @superandrew New stable version 1.61 of VS Code has been released. This version includes the fix for the certificate issue, so after updating VS Code editor to the new version, Expo debugging should work without problems. |
Hi I still have this issue, with vscode version 1.63.2 (user setup).
I get the following output:
This is my {
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Debug in Exponent",
"cwd": "${workspaceFolder}",
"type": "reactnative",
"request": "launch",
"platform": "exponent",
"expoHostType": "lan"
}
]
} |
Hi @artus and thanks for reporting. It seems that the certificate issue is related to this issue in VS Code and Electron. According to this comment the problem should be fixed after updating Electron to version 16 in VS Code. |
Thanks, that workaround seems to fix it! |
This bug doesn't seem to reproduce in the latest VSCode v1.66, so I'm closing the issue |
🐛 What is the bug? How can we reproduce it?
Please put here any steps, code or any information that can help us
reproduce the error on our side so we can fix it:
Some additional details. If I launch directly from CLI 'expo start -c', app is able to run properly. I also created a brand new project from scratch using 'expo init' and simply ran the basic tabbed scaffold app and same issue occurred.
Expected behavior
App runs on the device as normal.
Debug output
Debug Console
React Native output channel
Developer Tools console
Environment
Please tell us about your system and your project:
npx react-native doctor
ornpx expo doctor
if your project is using Expo:envinfo
:The text was updated successfully, but these errors were encountered: