Skip to content
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

Can't connect to FCM or register with Expo #5

Closed
s8wa2 opened this issue Oct 1, 2021 · 2 comments
Closed

Can't connect to FCM or register with Expo #5

s8wa2 opened this issue Oct 1, 2021 · 2 comments

Comments

@s8wa2
Copy link

s8wa2 commented Oct 1, 2021

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.

image

@liamcottle
Copy link
Owner

Thanks for the report.

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.

@liamcottle
Copy link
Owner

Fixed in v1.0.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants