You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can't seem to get atlas working anymore. Was working a week or so back, now has issues. FCM and Expo statuses remain constant and don't seem to work. Does not fix itself after logging out / in again.
Problem still persists even after
Updating to 1.0.3 and manually clearing saved data.
Testing multiple separate steam account
Testing on different devices
See attached images.
The text was updated successfully, but these errors were encountered:
I've just investigated this, and it turns out it's not an issue with FCM at all. I had a bug in Atlas where an Expo error was passed back to the FCM error handler. This has been fixed in master. So it will correctly show this as an Expo Status error and not an FCM Status error.
Moving back to the actual issue... The Expo certificate (for https://exp.host) is being marked as expired. After looking into this, it's not actually expired, but one of the Root CA certs for Let's Encrypt has expired. More info on that here: DST Root CA X3
This isn't an issue for the latest browsers etc, but Atlas uses Electron and it appears there's a missing config for how it verifies the full chain of certificates electron/electron#31212 and a fix has been merged into Electron here electron/electron#31213
Unfortunately Atlas is using Electron v11 and according to this comment the fix is only going to be backported to Electron v12+.
Ideally, we would upgrade to Electron v15/v16 but I don't have too much time for this at the moment.
For now, I am going to disable SSL certificate verification for the api call to register for an Expo Token and then I'll push out a new version.
Can't seem to get atlas working anymore. Was working a week or so back, now has issues. FCM and Expo statuses remain constant and don't seem to work. Does not fix itself after logging out / in again.
Problem still persists even after
See attached images.
The text was updated successfully, but these errors were encountered: