ReferenceError: SharedArrayBuffer is not defined #263

avi12 · 2021-10-02T18:59:53Z

Describe the bug
Getting a ReferenceError: SharedArrayBuffer is not defined error after [info] ffmpeg-core.js script loaded

To Reproduce
Simply initialize FFmpeg on Firefox

Expected behavior
It should work as usual on Firefox, but it cannot properly initialize

Screenshots

Desktop (please complete the following information):

OS: Windows 10 x64 21H1
Browser: Firefox 92.0.1

Additional context
This is my repository

The text was updated successfully, but these errors were encountered:

RSWilli · 2021-10-06T10:27:40Z

as the Readme states:

SharedArrayBuffer is only available to pages that are cross-origin isolated. So you need to host your own server with Cross-Origin-Embedder-Policy: require-corp and Cross-Origin-Opener-Policy: same-origin headers to use ffmpeg.wasm.

SharedArrayBuffer is not available until you do add these headers

and in Safari it will never be available, because SharedArrayBuffer is disabled there

https://caniuse.com/sharedarraybuffer

avi12 · 2021-10-06T11:15:38Z

The reason I made my browser extension in the first place is that it doesn't need a server to work but instead use the user's computational power

MemoryAndDream · 2021-10-13T08:35:01Z

as the Readme states:

SharedArrayBuffer is only available to pages that are cross-origin isolated. So you need to host your own server with Cross-Origin-Embedder-Policy: require-corp and Cross-Origin-Opener-Policy: same-origin headers to use ffmpeg.wasm.

SharedArrayBuffer is not available until you do add these headers

and in Safari it will never be available, because SharedArrayBuffer is disabled there

https://caniuse.com/sharedarraybuffer

I add these headers when getting my html page and it works.But now I have trouble with add third party JS in my page,which will be blocked by cross-origin isolated. Any work around method to use third party JS in my video edit page(with wasm)?

donatj · 2021-10-15T21:20:59Z

Dumb question from someone who knows nothing - what would it take / would it even be possible to rewrite this not to use SharedArrayBuffer?

Given the current state of how difficult it is to use, seems like if it's possible, it'd be worth it.

avi12 · 2021-10-15T21:26:52Z

Even if you manage to rewrite it in a different way, I doubt the progress of releases
A couple of pull requests have been merged (including my #232), but the last release was on June 14

Fanna1119 · 2021-11-09T06:37:08Z

If there is someone using vite for development environment.
https://github.com/chaosprint/vite-plugin-cross-origin-isolation

Zophiel · 2021-12-02T13:54:41Z

@Fanna1119 This doesn't solve the issue in a live environment

martins-a · 2022-01-07T00:45:23Z

Hello, in react easier way is using this library: https://create-react-app.dev/docs/proxying-api-requests-in-development/#configuring-the-proxy-manually

With this you can create a proxy, in the proxy you will be able to set the headers, example bellow:

module.exports = function (app) {
    app.use(function (req, res, next) {
        res.setHeader("Cross-Origin-Opener-Policy", "same-origin");
        res.setHeader("Cross-Origin-Embedder-Policy", "require-corp");
        next();
    });

    app.use(
        '/api',
        createProxyMiddleware({
          target: 'http://localhost:8080',
          changeOrigin: true,
        })
      );
};

I really don't know how to deal with this in SPAs production env, but for server-client applications it should work fine (for example react SSR).

For ffmpeg.wasm. See also: ffmpegwasm/ffmpeg.wasm#263

zack-pronto · 2022-04-08T19:13:55Z

Safari now has support for SharedArrayBuffer as of March 2022 https://caniuse.com/sharedarraybuffer

usr-ein · 2022-06-07T08:52:54Z

Hello, in react easier way is using this library: https://create-react-app.dev/docs/proxying-api-requests-in-development/#configuring-the-proxy-manually

With this you can create a proxy, in the proxy you will be able to set the headers, example bellow:

I had to tune your example for it to work with React. Beware that even when running a Typescript react project, you need to write this as a setupProxy.JS (and not .TS):

module.exports = function (app) {
    app.use(function (req, res, next) {
        res.setHeader("Cross-Origin-Opener-Policy", "same-origin");
        res.setHeader("Cross-Origin-Embedder-Policy", "require-corp");
        next();
    });
};

For SPAs, you don't need to create a proxy middleware, you just need to intercept the req/resp and add your headers.

Also, you don't need to install http-proxy-middleware at all for this to work. It just works straight out of the box on React apps.

Why we need those headers, according to the doc.

hankchiutw · 2022-06-11T03:31:12Z

For developing in vite, you can set the vite.config.js:

export default {
  server: {
    headers: {
      'Cross-Origin-Embedder-Policy': 'require-corp',
      'Cross-Origin-Opener-Policy': 'same-origin',
    },
  },
};

SeiwonPark · 2022-06-30T13:59:51Z

Anyone who's using Next.js,

here's my next.config.js file and it works perfectly

// next.config.js

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  async headers() {
    return [
      {
        source: '/',
        headers: [
          {
            key: 'Cross-Origin-Embedder-Policy',
            value: 'require-corp',
          },
          {
            key: 'Cross-Origin-Opener-Policy',
            value: 'same-origin',
          },
        ],
      },
    ];
  },
};

module.exports = nextConfig;

filmo · 2022-07-18T01:54:00Z

I've created a setupProxy.js file for my React app, and have installed http-proxy-middleware suggested on the link, but the following code doesn't seem to work for me.

module.exports = function (app) {
    app.use(function (req, res, next) {
        res.setHeader("Cross-Origin-Opener-Policy", "same-origin");
        res.setHeader("Cross-Origin-Embedder-Policy", "require-corp");
        next();
    });
};

It doesn't seem like this module.exports is getting called when I run npm start I continue to get the error Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined.

I'm trying to follow along this React/ffmpeg WASM tutorial. I'm using Chrome 103, ffmpeg wasm 0.10.0, snowpack 2.1, react 17.0.2

khaled-shaaban · 2022-07-31T12:42:25Z

as the Readme states:

SharedArrayBuffer is only available to pages that are cross-origin isolated. So you need to host your own server with Cross-Origin-Embedder-Policy: require-corp and Cross-Origin-Opener-Policy: same-origin headers to use ffmpeg.wasm.

SharedArrayBuffer is not available until you do add these headers

and in Safari it will never be available, because SharedArrayBuffer is disabled there

https://caniuse.com/sharedarraybuffer

It is now available though, no?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#browser_compatibility

cleandevcode · 2022-08-02T18:45:43Z

module.exports = function (app) {
    app.use(function (req, res, next) {
        res.setHeader("Cross-Origin-Opener-Policy", "same-origin");
        res.setHeader("Cross-Origin-Embedder-Policy", "require-corp");
        next();
    });
};

It is working on my side (React : 17.0.2, ffmpeg wasm: 0.10.3, chrome 103), but all the social logins (google, Microsoft, apple) does not work. All return the error saying pop up is closed by user.

Will be any solutions?

kiradea · 2023-01-17T07:53:41Z

anyone use UmiJS ?

donsaale5722 · 2023-03-20T07:00:02Z

Permanant solution of Shared Array buffer is not define in react js when i am include fbsdk in my project

#484 #483 #190 #482 #402 #121 #469

hlp-pls · 2023-04-20T04:00:18Z

for someone working with php, writing this code to the php file that contains the html document worked for me.

<?php
header("Cross-Origin-Embedder-Policy: require-corp");
header("Cross-Origin-Opener-Policy: same-origin");
?>

AlRodriguezGar14 · 2023-05-12T01:26:33Z

Has anyone found a solution for Nuxt 3? It did not manage to overcome this issue.

Whenever I load ffmpeg, I get the error, and establishing these headers did not help.
f1f71c-7747-4977-969e-ea0d6790910b:22 Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined at b2f1f71c-7747-4977-969e-ea0d6790910b:22:175 at Object.load (createFFmpeg.js:117:20) at async load (app.vue:15:3) (

SrLeet03 · 2023-07-01T22:23:44Z

For next js ,having following type of config worked for me.

`/** @type {import('next').NextConfig} */
const nextConfig = {
reactStrictMode: true,
async headers() {
return [
{
source: '/',
headers: [
{
key: 'Cross-Origin-Embedder-Policy',
value: 'require-corp',
},
{
key: 'Cross-Origin-Opener-Policy',
value: 'same-origin',
},
],
},
]
}

webpack(config, { webpack }) {
config.module.rules.push({
test: /.svg$/,
use: ['@svgr/webpack'],
})

config.plugins.push(
  new webpack.IgnorePlugin({
    resourceRegExp: /^\.\/wordlists\/(?!english)/,
    contextRegExp: /bip39\/src$/,
  })
)

config.resolve.alias = {
  ...config.resolve.alias,
  assets: getSharedPath('assets'),
  components: getSharedPath('components'),
  containers: getSharedPath('containers'),
  layouts: getSharedPath('layouts'),
  lib: getSharedPath('lib'),
  screens: getSharedPath('screens'),
  store: getSharedPath('store'),
  styles: getSharedPath('styles'),
}

return config

}
env: {

},
}

module.exports = nextTranslate(withTM(withPWA(nextConfig)))`

tgraupmann · 2023-07-12T21:27:57Z

All the sudden, like right now, the headers are not enough. There's an experimental Chrome flag but even that doesn't expose the SharedMemoryBuffer. It worked yesterday and even 10 minutes ago...

This WAS my workaround - https://vercel.com/guides/fix-shared-array-buffer-not-defined-nextjs-react

I have all the headers set via php. I confirmed the headers were set in the response.

header("Cross-Origin-Opener-Policy: same-origin");
header("Cross-Origin-Embedder-Policy: require-corp");

Broken in Edge/Chrome.

Firefox is still okay.

WebView2 browser is okay - https://learn.microsoft.com/en-us/microsoft-edge/webview2/samples/webview2browser?source=recommendations

I restarted my Chrome and the issue seems to have gone away. So I'm not sure what caused it. It's just odd that Chrome/Edge had the issue at the same time.

nibk · 2023-07-13T00:29:11Z

I had the same issue just start recently on a Chrome 114 build using a different wasm project. Previously I had NOT enabled:

Cross-Origin-Opener-Policy

I only enabled

Cross-Origin-Embedder-Policy

and everything worked. Now the Opener policy seems to be required also.

dataexcess · 2023-07-13T08:20:41Z

Has anyone found a solution for Nuxt 3? It did not manage to overcome this issue.

Whenever I load ffmpeg, I get the error, and establishing these headers did not help. f1f71c-7747-4977-969e-ea0d6790910b:22 Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined at b2f1f71c-7747-4977-969e-ea0d6790910b:22:175 at Object.load (createFFmpeg.js:117:20) at async load (app.vue:15:3) (

I am also using nuxt 3. DId you find a solution for this?

AlRodriguezGar14 · 2023-07-13T08:35:01Z

Has anyone found a solution for Nuxt 3? It did not manage to overcome this issue.
Whenever I load ffmpeg, I get the error, and establishing these headers did not help. f1f71c-7747-4977-969e-ea0d6790910b:22 Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined at b2f1f71c-7747-4977-969e-ea0d6790910b:22:175 at Object.load (createFFmpeg.js:117:20) at async load (app.vue:15:3) (

I am also using nuxt 3. DId you find a solution for this?

Sadly not @dataexcess. I had to move to React to make it work.

dataexcess · 2023-07-13T08:44:47Z

Has anyone found a solution for Nuxt 3? It did not manage to overcome this issue.
Whenever I load ffmpeg, I get the error, and establishing these headers did not help. f1f71c-7747-4977-969e-ea0d6790910b:22 Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined at b2f1f71c-7747-4977-969e-ea0d6790910b:22:175 at Object.load (createFFmpeg.js:117:20) at async load (app.vue:15:3) (

I am also using nuxt 3. DId you find a solution for this?

Sadly not @dataexcess. I had to move to React to make it work.

Hey! Using this nuxt plugin "nuxt-security" fixed it for me ! :D

https://snyk.io/blog/adding-security-to-nuxt-3/

tgraupmann · 2023-07-14T17:33:14Z

I can still reproduce the issue. If you use a lot of memory by using a canvas element and capture a lot of frames with getImageData into memory, somehow the added memory knocks out the settings. And even if both headers are present you get the SharedMemoryBuffer error.

I thought the workaround was to kill all your browser instances and relaunch. But it still happens so I have to use one of the browsers that still works.

Hmmm Firefox is showing duplicate headers, that might be the problem.

I had a .htaccess adding the headers and php adding the headers. So if you have a duplicate header it is discarded and SharedMemoryBuffer goes away.

After I fixed the duplicate header issue, it's working normally.

gabrielstuff · 2023-09-01T14:25:22Z

For anyone trying to find a solution when hosting on netlify for instance, you can use : https://github.com/gzuidhof/coi-serviceworker which makes it available.

iAmInActions · 2023-09-08T17:26:08Z

So, ive run into this issue too now. I added the stuff to my htaccess but its not working. When running the included example server on my local machine it works but when running it on my remote system under apache2, firefox keeps complaining. I have tried putting it in the .htaccess, in php and even tried writing it from javascript after the page loaded (which doesnt work btw but still tried it because i am really desperate to get this working). For htaccess and php it shows up in firefox when looking at the header but the browser seems to just ignore it and throws the error anyways. The same happens in chrome too. If anyone can help me out with that id be really thankful.

Bessonov · 2023-11-17T15:31:30Z

I think this issue could be closed because there are multiple solutions presented. According to the third point in https://caniuse.com/?search=SharedArrayBuffer, this is the way to enable support. If this doesn't work for your browser, consider opening an issue in the browser's issue tracker.

jumpjack · 2024-03-04T13:30:12Z

How to solve this issue using Github Pages?

WesleyBatista · 2024-03-05T18:51:03Z

How to solve this issue using Github Pages?

@jumpjack, out of curiosity specifically to the Github Pages deployment part, I tried out the vanilla-app version and it worked "out of the box": https://wesleybatista.github.io/ffmpeg.wasm-gh-pages/trim.html - source

Regarding original issue, maybe it's worth mentioning that headers solution above also worked for me, deploying an sveltekit app using firebase. Wonky setup, but working. Demo

jumpjack · 2024-03-06T08:29:11Z

It does not work "out of the box" for me, forking and enabling pages is not enough, needed files are not found.
I tried manual downloadin and unpacking and storing in my github folders, but ffmpeg.wasm is >25MB so I can't upload by browser.
Maybe I should run a github action? I have no idea about how they work.

CodyBontecou · 2024-03-17T08:31:34Z

For developing in vite, you can set the vite.config.js:

export default {
  server: {
    headers: {
      'Cross-Origin-Embedder-Policy': 'require-corp',
      'Cross-Origin-Opener-Policy': 'same-origin',
    },
  },
};

This doesn't seem to be working anymore, at least when hosting on Vercel.

smithmich12 · 2024-04-04T21:48:07Z

For developing in vite, you can set the vite.config.js:
export default {
  server: {
    headers: {
      'Cross-Origin-Embedder-Policy': 'require-corp',
      'Cross-Origin-Opener-Policy': 'same-origin',
    },
  },
};
This doesn't seem to be working anymore, at least when hosting on Vercel.

I was able to get this to work with vite by adding a vercel.json file to the root folder of my project. I am now running into different issues but my SharedArrayBuffer error is gone on vercel now.

{
    "headers": [
        {
            "source": "/(.*)",
            "headers": [
                { 
                    "key": "Cross-Origin-Embedder-Policy",
                    "value": "require-corp"
                },
                {
                    "key": "Cross-Origin-Opener-Policy", 
                    "value": "same-origin"
                }
            ]
        }
    ]
}

syjf · 2024-04-18T10:19:04Z

要在 vite 中开发，您可以设置vite.config.js：

export default {
  server: {
    headers: {
      'Cross-Origin-Embedder-Policy': 'require-corp',
      'Cross-Origin-Opener-Policy': 'same-origin',
    },
  },
};

After adding, the iframe and server images cannot be accessed. How can I solve this problem

marwie · 2024-06-11T14:32:24Z

要在 vite 中开发，您可以设置vite.config.js：
export default {
  server: {
    headers: {
      'Cross-Origin-Embedder-Policy': 'require-corp',
      'Cross-Origin-Opener-Policy': 'same-origin',
    },
  },
};
After adding, the iframe and server images cannot be accessed. How can I solve this problem

This might help you: https://blog.stackblitz.com/posts/cross-browser-with-coop-coep/

If CORS is enabled on external resources like images, scripts, stylesheets or videos, 
they have to be explicitly loaded by using the [crossorigin](https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/crossOrigin) attribute. 
The default value for this attribute is anonymous, which means that credentials such as cookies or http authentication will only be sent if the resources are fetched from the same origin. 
If the image is loaded from a different origin, all information is stripped so that only information publicly available is sent between client and server.

try <img crossorigin="anonymous" src="..." />

nica0012 · 2024-06-26T13:32:38Z

I am having the same issue as well, i am using vite and am hosting my project on cpanel. It seems with the vite config setting the headers I am able to make it work on desktop, but not mobile.

On mobile browsers it works by setting the cors headers in my htaccess file, but when I do this I can no longer load data from my third party libraries.

I've been stuck on this issue for 2 weeks now trying to get into prod...

subham827 · 2024-06-29T08:20:29Z

as the Readme states:

SharedArrayBuffer is only available to pages that are cross-origin isolated. So you need to host your own server with Cross-Origin-Embedder-Policy: require-corp and Cross-Origin-Opener-Policy: same-origin headers to use ffmpeg.wasm.

SharedArrayBuffer is not available until you do add these headers
and in Safari it will never be available, because SharedArrayBuffer is disabled there
https://caniuse.com/sharedarraybuffer

I add these headers when getting my html page and it works.But now I have trouble with add third party JS in my page,which will be blocked by cross-origin isolated. Any work around method to use third party JS in my video edit page(with wasm)?

Please do share any other work around

gazreyn · 2024-06-30T08:36:04Z

Has anyone found a solution for Nuxt 3? It did not manage to overcome this issue.
Whenever I load ffmpeg, I get the error, and establishing these headers did not help. f1f71c-7747-4977-969e-ea0d6790910b:22 Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined at b2f1f71c-7747-4977-969e-ea0d6790910b:22:175 at Object.load (createFFmpeg.js:117:20) at async load (app.vue:15:3) (

I am also using nuxt 3. DId you find a solution for this?

Sadly not @dataexcess. I had to move to React to make it work.

Hey! Using this nuxt plugin "nuxt-security" fixed it for me ! :D

https://snyk.io/blog/adding-security-to-nuxt-3/

For anyone using Nuxt 3, you need to set headers for both nuxt routes and for vite

For example

export default defineNuxtConfig({
  routeRules: {
    '/**': {
      headers: {
        'Cross-Origin-Opener-Policy': 'same-origin',
        'Cross-Origin-Embedder-Policy': 'require-corp',
      },
    },
  },
  vite: {
    optimizeDeps: {
      exclude: ['@ffmpeg/ffmpeg', '@ffmpeg/util'],
    },
    server: {
      headers: {
        'Cross-Origin-Opener-Policy': 'same-origin',
        'Cross-Origin-Embedder-Policy': 'require-corp',
      },
    },
  },
});

omitchen · 2024-10-06T10:57:56Z

Anyone who's using Next.js,

here's my next.config.js file and it works perfectly

// next.config.js

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  async headers() {
    return [
      {
        source: '/',
        headers: [
          {
            key: 'Cross-Origin-Embedder-Policy',
            value: 'require-corp',
          },
          {
            key: 'Cross-Origin-Opener-Policy',
            value: 'same-origin',
          },
        ],
      },
    ];
  },
};

module.exports = nextConfig;

it's not work new, Next 13.2.1 + chrome 126 + cf deploy, localhost is OK? who can help me

jasonz1987 · 2024-10-16T05:31:00Z

Anyone who's using Next.js,
here's my next.config.js file and it works perfectly

// next.config.js

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  async headers() {
    return [
      {
        source: '/',
        headers: [
          {
            key: 'Cross-Origin-Embedder-Policy',
            value: 'require-corp',
          },
          {
            key: 'Cross-Origin-Opener-Policy',
            value: 'same-origin',
          },
        ],
      },
    ];
  },
};

module.exports = nextConfig;

it's not work new, Next 13.2.1 + chrome 126 + cf deploy, localhost is OK? who can help me

it's also not working on nextjs 14.2

saradotdev · 2024-10-24T18:59:54Z

This worked for me too for vercel. Thanks a ton!

zeek0x added a commit to zeek0x/emogif that referenced this issue Feb 18, 2022

Add custom header to netlify header file.

d444734

For ffmpeg.wasm. See also: ffmpegwasm/ffmpeg.wasm#263

zeek0x added a commit to zeek0x/emogif that referenced this issue Feb 18, 2022

Add custom header to netlify header file.

df52357

For ffmpeg.wasm. See also: ffmpegwasm/ffmpeg.wasm#263

camelcrush referenced this issue in camelcrush/wetube-clone Feb 22, 2022

Transcode video: ffmpeg.wasm

29e127c

avi12 mentioned this issue Mar 27, 2022

It is no longer working. avi12/youtube-downloader#2

Closed

dvnrsn mentioned this issue May 22, 2022

ffmpeg-core unpkg NotSameOriginAfterDefaultedToSameOriginByCoep ffmpegwasm/react-app#16

Open

my-roki mentioned this issue Jul 4, 2022

ReferenceError: SharedArrayBuffer is not defined my-roki/Rokitube#6

Open

filmo mentioned this issue Jul 18, 2022

lessons/wasm-video-to-gif/ fireship-io/fireship.io#856

Open

Cooper4111 mentioned this issue Aug 5, 2022

Chrome Manifest V3 support alyssaxuu/screenity#152

Closed

jumpjack mentioned this issue Mar 4, 2024

Chrome and Edge not support multi-thread (Test in playground) #530

Open

ReferenceError: SharedArrayBuffer is not defined #263

ReferenceError: SharedArrayBuffer is not defined #263

Comments

avi12 commented Oct 2, 2021

RSWilli commented Oct 6, 2021

avi12 commented Oct 6, 2021

MemoryAndDream commented Oct 13, 2021

donatj commented Oct 15, 2021

avi12 commented Oct 15, 2021

Fanna1119 commented Nov 9, 2021

Zophiel commented Dec 2, 2021

martins-a commented Jan 7, 2022 • edited Loading

zack-pronto commented Apr 8, 2022

usr-ein commented Jun 7, 2022 • edited Loading

hankchiutw commented Jun 11, 2022

SeiwonPark commented Jun 30, 2022 • edited Loading

filmo commented Jul 18, 2022

khaled-shaaban commented Jul 31, 2022

cleandevcode commented Aug 2, 2022

kiradea commented Jan 17, 2023

donsaale5722 commented Mar 20, 2023

hlp-pls commented Apr 20, 2023

AlRodriguezGar14 commented May 12, 2023

SrLeet03 commented Jul 1, 2023

tgraupmann commented Jul 12, 2023 • edited Loading

nibk commented Jul 13, 2023

dataexcess commented Jul 13, 2023

AlRodriguezGar14 commented Jul 13, 2023

dataexcess commented Jul 13, 2023

tgraupmann commented Jul 14, 2023 • edited Loading

gabrielstuff commented Sep 1, 2023

iAmInActions commented Sep 8, 2023

Bessonov commented Nov 17, 2023

jumpjack commented Mar 4, 2024

WesleyBatista commented Mar 5, 2024

jumpjack commented Mar 6, 2024 • edited Loading

CodyBontecou commented Mar 17, 2024

smithmich12 commented Apr 4, 2024

syjf commented Apr 18, 2024

marwie commented Jun 11, 2024 • edited Loading

nica0012 commented Jun 26, 2024

subham827 commented Jun 29, 2024

gazreyn commented Jun 30, 2024 • edited Loading

omitchen commented Oct 6, 2024

jasonz1987 commented Oct 16, 2024

saradotdev commented Oct 24, 2024

martins-a commented Jan 7, 2022 •

edited

Loading

usr-ein commented Jun 7, 2022 •

edited

Loading

SeiwonPark commented Jun 30, 2022 •

edited

Loading

tgraupmann commented Jul 12, 2023 •

edited

Loading

tgraupmann commented Jul 14, 2023 •

edited

Loading

jumpjack commented Mar 6, 2024 •

edited

Loading

marwie commented Jun 11, 2024 •

edited

Loading

gazreyn commented Jun 30, 2024 •

edited

Loading