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

gatsby-plugin-manifest - Input file contains unsupported image format #28204

Closed
fmunirdev opened this issue Nov 20, 2020 · 6 comments
Closed
Labels
type: bug An issue or pull request relating to a bug in Gatsby

Comments

@fmunirdev
Copy link

Started facing this issue recently on the Nelify build. gatsby build works perfectly fine in the local env.

gatsby-config.js
    {
      resolve: `gatsby-plugin-manifest`,
      options: {
        name: `name`,
        short_name: `sname`,
        description: `desc`,
        lang: `en`,
        start_url: `/`,
        background_color: `#fff`,
        theme_color: `#a50f20`,
        display: `standalone`,
        icon: `static/assets/images/icon.png`,
        icon_options: { purpose: `maskable` },
      },
    },

Nelify Deploy Logs

Nelify Deploy Logs Screenshot

@fmunirdev fmunirdev added the type: bug An issue or pull request relating to a bug in Gatsby label Nov 20, 2020
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Nov 20, 2020
@vladar
Copy link
Contributor

vladar commented Nov 20, 2020

This sounds like is a duplicate of #20698

Likely happening because Netlify has global libvips installed that is incompatible with a local sharp version. The suggested solution is to re-install dependencies from scratch using SHARP_IGNORE_GLOBAL_LIBVIPS=true:

rm -rf node_modules &&
SHARP_IGNORE_GLOBAL_LIBVIPS=true yarn

We're marking this issue as answered and closing it for now but please feel free to comment and mention me if you would like to continue this discussion. We hope we managed to help and thank you for using Gatsby! 💜

@vladar vladar closed this as completed Nov 20, 2020
@vladar vladar removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Nov 20, 2020
holly-cummins added a commit to holly-cummins/gatsby-platform that referenced this issue Nov 12, 2021
holly-cummins added a commit to holly-cummins/gatsby-platform that referenced this issue Nov 15, 2021
holly-cummins added a commit to holly-cummins/gatsby-platform that referenced this issue Nov 15, 2021
@yiochen
Copy link

yiochen commented Jan 1, 2022

For anyone using Netlify and facing this issue, you can add the environment variable SHARP_IGNORE_GLOBAL_LIBVIPS with value true to https://app.netlify.com/sites//settings/deploys#environment

This fixed the issue for me.

@srianbury
Copy link

After the deploy failed, I was able to "Clear cache and retry deploy" and that build was successful
Screen Shot 2022-07-07 at 4 23 49 PM

@eindra
Copy link

eindra commented Aug 18, 2022

Setting the SHARP_IGNORE_GLOBAL_LIBVIPS fixed the issue for me! Thank you!

@TomaszWaszczyk
Copy link

Lost on that flag SHARP_IGNORE_GLOBAL_LIBVIPS so much time! Thanks @yiochen!

@jung-youjin
Copy link

Works like charm with the SHARP_IGNORE_GLOBAL_LIBVIPS variable setting and Clear cache and retry deploy! Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

No branches or pull requests

7 participants