# Gallery View in meeting SDK

**URL:** <https://devforum.zoom.us/t/gallery-view-in-meeting-sdk/122158>\
**Category:** Meeting SDK\
**Tags:** api, sdk\
**Created:** [December 9, 2024, 1:56pm UTC](https://devforum.zoom.us/t/gallery-view-in-meeting-sdk/122158 "2024-12-09T13:56:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![uitestingawsai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/uitestingawsai/32/65118_2.png) [@uitestingawsai](https://devforum.zoom.us/u/uitestingawsai)\
**Post date:** [December 9, 2024, 1:56pm UTC](https://devforum.zoom.us/t/gallery-view-in-meeting-sdk/122158/1 "2024-12-09T13:56:15Z")

</div>

When implementing Cross-Origin Isolation (COI) for the gallery view in Zoom, external connections are blocked, causing AWS S3-linked images to fail to load initially and only appear after refreshing the page. Without COI, the gallery view cannot be used, but with COI, the images don’t display directly. Attempts to enable COI for just one page have not yielded a solution yet.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [December 11, 2024, 9:05am UTC](https://devforum.zoom.us/t/gallery-view-in-meeting-sdk/122158/2 "2024-12-11T09:05:51Z")

</div>

Hi, thank you for posting on the Zoom Developer Forum, @uitestingawsai ! Have you tried different options for enabling SharedBufferArray? I’ve seen scenarios where specific settings can cause behavior similar to what you described. Here is our support documentation on this topic, which includes several options for enabling SharedBufferArray.

> **[Meeting SDK - web - SharedArrayBuffer - Zoom Developers](https://developers.zoom.us/docs/meeting-sdk/web/sharedarraybuffer/)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

---

<div class="post-metadata">

**Author:** ![uitestingawsai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/uitestingawsai/32/65118_2.png) [@uitestingawsai](https://devforum.zoom.us/u/uitestingawsai)\
**Post date:** [December 11, 2024, 10:57am UTC](https://devforum.zoom.us/t/gallery-view-in-meeting-sdk/122158/3 "2024-12-11T10:57:19Z")

</div>

@donte.zoom ok then let me try other option i have tried with this [GitHub - gzuidhof/coi-serviceworker: Cross-origin isolation (COOP and COEP) through a service worker for situations in which you can't control the headers (e.g. GH pages)](https://github.com/gzuidhof/coi-serviceworker)

can you suggest me a better methode which will adaptive of aws

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [December 12, 2024, 7:57pm UTC](https://devforum.zoom.us/t/gallery-view-in-meeting-sdk/122158/4 "2024-12-12T19:57:08Z")

</div>

Certainly, trying different options is the way to go, @uitestingawsai! As host environments change, it’s difficult to provide a one-size-fits-all solution. Trying different options will help better isolate the behavior you’re seeing and determine if it’s an environment issue as well!