Couldn't find type Upload in any of the schemas

[prajjwaldimri]

I was trying to get the file upload working in my graphql server by following
https://blog.apollographql.com/file-uploads-with-apollo-server-2-0-5db2f3f60675

In the article the author mentions that Apollo automatically adds the Upload type to the schema. However, when importing my typeDefs using graphql-import I am getting the error:

Error: Field file: Couldn't find type Upload in any of the schemas. at collectNode (/home/--/--/node_modules/graphql-import/src/definition.ts:154:15)

When adding scalar Upload to the schema.graphql file I get the error:

Error: There can be only one type named "Upload". at assertValidSDL (/home/--/--/node_modules/graphql/validation/validate.js:89:11)

Thanks

[daologger]

same here. Currently, I have to mix importSchema with gql like this to make it work:

const basicDefs = importSchema('./schema.graphql')

const mutationDefs = gql`
  # I have other mutation fields defined in basicDefs
  extend type Mutation {
    imageUpload(file: Upload!): File
  }
`

new ApolloServer({
  typeDefs: [basicDefs, mutationDefs], resolvers,
})

[mxstbr]

I am also running into this. Any ideas how to solve it?

[mxstbr]

As said in the OP:

When adding scalar Upload to the schema.graphql file I get the error:
Error: There can be only one type named "Upload". at assertValidSDL (/home/--/--/node_modules/graphql/validation/validate.js:89:11)

[maticzav]

Just noticed. (I deleted the comment). To my understanding, this happens because of the way graphql-import is implemented. While generating the imported schema, definition pool searches for all definitions mentioned in the file (this happens because graphql-import includes dependencies of the imported types as well as the imported types themselves.)

Because of that, it throws an exception that Upload is missing.

Did anyone perhaps test the behaviour with GraphQL Yoga?

I hope that helps with understanding, sorry for the previous answer.

[diegofly91]

Fix the error by putting the scheme const typeDefs = gql......and not importing the .graphql file

[felipeborba-dev]

I have the same problem, look at my server implementation

const { ApolloServer, gql } = require('apollo-server-express')
const { importSchema } = require('graphql-import')
const express = require('express')
const app = express()
const routes = require('./routes')


initServer();

function initServer() {
    try {
        
        const mutationDefs = gql`
            scalar Upload
            type Mutation {
            uploadFotoColaborador(file: Upload!): File!
            }
        `
        const resolvers = require('./resolvers')
        const context = require('./config/context')
        const schemaPath = './src/schema/index.graphql';
        const basicDefs = importSchema(schemaPath)
        const serverGraphQL = new ApolloServer({
            typeDefs:[basicDefs, mutationDefs],
            resolvers,
            context
        });

        serverGraphQL.applyMiddleware({ app, path: '/api' })
        app.use(express.json())
        app.use(routes)
        app.listen({ port: 4000 }, () => {
            console.log('Executando em localhost:4000')
        })
    }
    catch (error) {
        console.log(`Servidor não pode ser inicializado: ${error}`)
    }
}

[amiiit]

I'm still trying to get the whole setup working, but perhaps the following workaround might be of use to someone:

  const typeDefs = importSchema(__dirname + "/schema.graphql").replace(
    "scalar Upload",
    ""
  )

Makes the toolset happy, because scalar Upload is part of the schema file, and so apollo server isn't complaining anymore about double definition of the scalar Upload

EDIT: I can confirm, this workaround is working fine.

[felipeborba-dev]

@amiiit will perform the tests, thank you very much!

[hanselabreu]

@amiiit that doesn't work for me, I still get the error. I'm on version 0.7.1

[byteab]

the error is because importSchema throw an error if it find type Upload used but not defined in Schema.
and if you add the type "scalar Upload" the importSchema will pass but apollo server will complain because apollo server will also add a "scalar Upload" by default. and now your schema have two "scalar Upload".
I think apollo server must check if type Upload not defined in schema then add it.

the temporary solution is to remove "scalar Upload" after importSchema read it.
as @amiiit said

[hyochan]

This issue makes apollo-server upload useless. I hope, I can see a full workaround. Tried all the above solution and still having the problem.

[ardatan]

Available in 1.0.0!

[Dev-Addict]

I was having the same problem and by reading @hyochan comment i found out it's because of the name of scalar we put.
you can easily fix the problem by renaming the scalar. what i did was i renamed it to UploadFile and this fixed my problem