EAP ObjectStore experience

Forge
,
1

Hello all,

In order to have the object storage to work, how many EAPs do I need ?

My timeline:

2025-11-11

I registered for the FileUploader/FileCard EAP

2025-11-24

After some back and forth to get it properly activated, it worked: I could use the components and upload a file in the Object storage using the example code (with some tweaks).

2025-12-03

I came back to Object Storage after uploading elsewhere but I could not get build the upload URL anymore, it fails with a Forge platform failed to process runtime HTTP request - 400 - INVALID_CAPACITY.

I also get a lint warning a missing objectStore module. Sadly, this one is not documented, I went in the @forge/manifest to get the truth :-).

This made me add the objectStore module with a key and storageClass.

With that, my app cannot be deployed anymore:

Error: Manifest validation failed: Forge OS is not enabled for this app. You'll need to register it first. https://developer.atlassian.com/platform/forge/storage-reference/object-store/#object-store--eap- (requestId: d2fde350-067f-4b86-b51c-163cd95c841e)

So I requested to be allowed to this EAP too (still pending).

My questions:

  1. Are these EAPs related or am I just trying randomly?
  2. Are the error I describe related?
  3. Am I missing something to try this completely?
  4. Could this specific EAP(s) be documented a little bit more? — most page are out of date, have links to this community forum that show me a Page Not Found

Thanks in advance

2

Hey Magnus!
Thanks for sharing your concerns and for signing up for the EAPs.
To your main question: the BE (Object Store) and FE (FileUploader/FileCard) are two separate EAPs.

  • The Object Store EAP is the backend capability that gives you the objectStore module in the manifest and the storage capacity behind it.

  • The UI components EAP (FileUploader/FileCard) is a separate UI‑side EAP that we implemented to work with Object Store, but the components themselves aren’t strictly coupled to the Object Store feature flag as the UI Kit components can be used with other storage solutions. Our bridge and hook methods are coupled with Object Store EAP.

It’s really useful for us to see how the separate BE/FE EAPs show up in a real workflow and how it’s impacted you. We’ll take this feedback into account as we plan future joint EAPs with better cross-EAP documentation and potentially a unified signup form and flag.
Vicky,
Product Manager, Forge UI