I know this issue was already addressed regarding the requestConfluence discussion.
And according to staff members the solution was released on July 27, although I’m not sure this also includes the Storage api.
Just to confirm this error occurs for non-production environments, right? Trying to eliminate the possibility that you have different amounts of data in the different environments that could be causing this issue.
This happens if I deploy the app to either development or production, both stages seems to have this issue.
When I tunnel the app and serve it locally, the error goes away.
Is there any chance this would be fixed before you’re hackathon’s deadline?
I’ve built an entire Forge app, everything works perfectly, except for this issue.
Can you provide anymore context? It sounds like it is something specific to how you are using storage.
Can you post a sample app that has the minimum viable code to reproduce it?
Alternatively, have you tried messing with your own apps a bit to use storage in a different/simpler way? Trying to figure out is it happening any time you are using the storage API or just for specific calls you are making?
