Skip to content

Cover auth failure case before It looks like there are 0 files associated with this Apollo Project. #2689

@jsoref

Description

@jsoref

We have a graphql endpoint that requires authorization, when we properly pass --header "Authorization: Bearer ..." to apollo client:download-schema, things work nicely. When we don't, we get:

⚠️ It looks like there are 0 files associated with this Apollo Project. This may be because you don't have any files yet, or your includes/excludes fields are configured incorrectly, and Apollo can't find your files. For help configuring Apollo projects, see this guide: https://go.apollo.dev/t/config

"⚠️ It looks like there are 0 files associated with this Apollo Project. " +
"This may be because you don't have any files yet, or your includes/excludes " +
"fields are configured incorrectly, and Apollo can't find your files. " +
"For help configuring Apollo projects, see this guide: https://go.apollo.dev/t/config"

This is fairly misleading/confusing and has resulted in myself and others wasting a lot of time trying to figure out if something else was wrong.

If apollo encounters a 4xx series error (especially 400/401), it'd be really helpful if it reported the url and error instead of just providing the current output.

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