404 when querying license API from Forge Remote in dev environment with `--license active`

Forge
,
1

Hello,

I’ve found that I can test licensing in a Forge app if I forge install a dev environment with --license active or --license inactive. Surprisingly, (I’d appreciate some clarity here), the old Connect license API works for our Forge app—specifically, from our Forge Remote—when we use the Connect key specified in the Forge manifest (we’re migrating our apps from Connect to Forge). But we’re working on moving to the new Forge license API instead.

However, I’ve found that my Forge remote consistently gets 404 errors when it query the Forge license API using a development environment. I suspect the issue is that --license active doesn’t create a real license that would be retrievable via the license API. Is that correct? And if so, what is the appropriate way to test the license API? Naturally, we don’t want to push untested code to production, but I don’t see any other way to do this at the moment.

2

Better if you read this discussion here Clarity on Forge License shape in APIs but bottom line is that on development the licensing API doesn’t really mean anything. You can push whatever to display whatever as the actual payload doesn’t render. You need to be in a production environment or probably make an assumption of how the actual payload is supposed to work in production then design your code in that structure.

3

I filed a ticket with Atlassian. The problem turned out to be a documentation bug. They had the wrong URL in their Forge license API docs.

The license API seems to work with both production and developer environments.