GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Chapter "Authentication-State" (web-master) - Logging In does not work ! · Issue #25 · javascripteverywhere/web

Chapter "Authentication-State" (web-master) - Logging In does not work ! #25

New issue
Copy link
New issue
Copy link
Open
Open
Chapter "Authentication-State" (web-master) - Logging In does not work !#25
Copy link

Description

@MarioG8
MarioG8
opened on Jan 18, 2021
Issue body actions

Console:
Uncaught (in promise) Error: Network error: Response not successful: Received status code 400
ApolloError ApolloError.js:26
error QueryManager.js:138
notifySubscription Observable.js:140
onNotify Observable.js:179
error Observable.js:240
error observables.js:12
error observables.js:12
notifySubscription Observable.js:140
onNotify Observable.js:179
error Observable.js:240
notifySubscription Observable.js:140
onNotify Observable.js:179
error Observable.js:240
createHttpLink createHttpLink.js:93

Files from project still don't solve the problem.
Best Regards and Have a nice Coding! :)

Reacted by MarioG8

Activity

  1. MarioG8
    changed the title [-]Authentication-State (web-master) Logging In does not work ! [/-] [+]Chapter "Authentication-State" (web-master) - Logging In does not work ![/+] on Jan 18, 2021
  2. MarioG8 commented on Jan 21, 2021

    @MarioG8
    MarioG8
    on Jan 21, 2021
    Author
    More actions

    I think I have found the solution of this issue...! :-) I had to take it back a bit to /api/schema.js
    I deleted the !"username"! from type Mutation - signIn
    This seemed logical because we do not have such a field in signin.js file in
    web/solutions/04-Authentication-State/pages/signin.js /
    GraphQL requires you to be explicit about specifying which fields you would like returned from your query. Am I right?
    Now everything works great so far ...I can log in and log out and application does not break :)
    I wanted to make a "pull request" but I'm ashamed ... Please analyse my code and grant permission for a "pull request" if everything works fine...?!?
    See You Soon and Have a nice Day or Night whatever you want;)

    Reacted by MarioG8
  3. MarioG8
    closed this as completedon Jan 21, 2021
  4. MarioG8
    reopened this on Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.