Skip to content
This repository has been archived by the owner on Jul 15, 2018. It is now read-only.

White page after starting server #43

Open
happel opened this issue Aug 20, 2017 · 5 comments
Open

White page after starting server #43

happel opened this issue Aug 20, 2017 · 5 comments

Comments

@happel
Copy link

happel commented Aug 20, 2017

After installing and starting the latest commit my browser only displays a white page with a small bar running across when I direct the browser to the login page. On the mainpage it only shows "This is HomePage components !"

Console shows only this:

user@ubuntu:~/tinder/tinder$ npm start

> [email protected] start /home/user/tinder/tinder
> cross-env NODE_ENV=development babel-watch server

Server started ✓

Access URLs:
-----------------------------------
Localhost: http://localhost:3000
      LAN: http://192.168.109.133:3000
-----------------------------------
Press CTRL-C to stop

webpack built 6ea8c893d8614d4423be in 12546ms


@luccasmf
Copy link

I'm having same issue, got any solution ?

@chdhr-harshal
Copy link

same issue here

@crorodriguezro
Copy link

It's and authentication problem. As a workarount I reinstalled the chrome extension and updated the CHROME_EXTENSION_ID in Sagas.

@eddiewang
Copy link
Collaborator

project is no longer being maintained - but @crorodriguezro has the right idea here. you need to update the extension id (or pass in the auth token)

@jdunk
Copy link
Contributor

jdunk commented Dec 2, 2017

Same issue here - this seems to have started only after the last time I logged out of facebook, so I'm guessing that facebook has changed 1 or more details about how their auth works and that this new way breaks flamite. I end up on an almost-entirely-white (except for only a thin horizontal gray line 60px from the top) page with the URL:

http://localhost:3000/login/EAAGm0PX4ZCpsBAMwt2a5vbN0EvkIZCkGBAg4r4UT5JZCACXpAmx6bsxcdtCtJwqZC9Qqg5Sanw5Y2r8UP6g3tOx9hzzIxZCCp0rJszpjNVmL3ZAVyg1YEXXtco9rYvYBzrnn2yI9hNT1c3KUd1zDu7AQ8ZC0qJ2gHETdIKXCTvQvnkvZA6gGLh4HjD8FMUtGZBR2...

Deleting and then reinstalling the extension did absolutely nothing. I even ended up with exactly the same Chrome Extension ID. Can anyone else confirm/verify this? Anyone know anything about a recent change in Facebook's auth details?

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

No branches or pull requests

6 participants