Sentry with async function nextConfig not working

[AbhiPrasad]

Discussed in #7433

^{Originally posted by Supermog March 13, 2023}
So I have a project that I added Sentry to, but the problem is that I have the nextConfig variable as an async function which the withSentryConfig doesn't accept. My next.config.js file looks like this:

const { withSentryConfig } = require('@sentry/nextjs');

const prismic = require('@prismicio/client');

const sm = require('./sm.json');

/** @type {import('next').NextConfig} */
const nextConfig = async () => {
  const client = prismic.createClient(sm.apiEndpoint);

  const repository = await client.getRepository();
  const locales = repository.languages.map(lang => lang.id);

  return {
    reactStrictMode: true,
    swcMinify: true,
    compiler: {
      styledComponents: true,
    },
    i18n: {
      // These are all the locales you want to support in
      // your application
      locales: locales,
      // This is the default locale you want to be used when visiting
      // a non-locale prefixed path e.g. `/hello`
      defaultLocale: locales[0],
      localeDetection: false,
    },
  };
};

module.exports = withSentryConfig(
  nextConfig,
  { silent: true },
  { hideSourcemaps: true },
);

I've also played around with it and using await on the nextConfig argument or calling the function also does not work. I've tried converting it to .then blocks but that also does not work.
Without Sentry it works well because nextjs accepts nextConfig as an async function but Sentry does not. Is there a workaround to this?

"@sentry/nextjs": "^7.42.0",
"next": "13.1.2",
"react": "18.2.0",

[AbhiPrasad]

From @Supermog

#7433 (reply in thread)

error - Error: Invalid locale returned from getStaticPaths for /[uid], the locale en-gb is not specified in next.config.js
   at /home/supermog/Repos/marketing-cms/node_modules/next/dist/build/utils.js:667:23
   at Array.forEach (<anonymous>)
   at Object.buildStaticPaths (/home/supermog/Repos/marketing-cms/node_modules/next/dist/build/utils.js:621:17)
   at processTicksAndRejections (node:internal/process/task_queues:96:5) {
 type: 'Error',
 page: '/[uid]'
}

This is the error message. It occurs whenever I go to a URL that the 404.tsx component should handle.