Multi platform app throws "Failed to validate FCT" on jira:fullPage

Forge Forge Platform and Tools
1

We are currently trying to implement a forge app for jira and confluence. So following the tutorial we added the compatiblity section to the manifest making jira the required app and confluence optional.

  compatibility:
    confluence:
      required: false
    jira:
      required: true

Now as soon as we additionally connect confluence every resolver call fails in Jira with the message

 "errors": [
                {
                    "message": "Failed to validate FCT: 'contextIds' claim mismatch",
                    "extensions": {
                        "__typename": "GenericMutationErrorExtension",
                        "errorType": "FCT_VALIDATION_CLAIM_MISMATCH",
                        "statusCode": 400
                    }
                }
            ]

This does only happen if we use the Fullpage module. Does anyone know what we do wrong here?

2

hi @SandroHerrmann , have you installed this app on both Jira and Confluence? Cross app compatibility will work when forge-apps are installed in all compatible apps.

3

Hi,

yes its installed on both Jira And Confluence. Now I seem to get closer to the issue as I noticed that it only happens when doing calls from the jira:fullPage module. So maybe i do something wrong there, or there is a configuration i have missed.

Just checked… seems not. Is this a potential bug?

4

Hi @SandroHerrmann, thanks for reaching out. We’re rolling out a fix for this over the next few days. If you can provide me with your test site’s Cloud ID in the meantime I can make it available for you to verify earlier

5

Hi @TimothyVanDyke,

thanks for the quick reply. You guys are awsome. Its totally fine for us if its released in the next days or week. We can test our main features on Jira for now. Support also mentioned an official ticket for it but only told me to vote on it.

6

I’m also affected by this. @TimothyVanDyke, was the fix already rolled out? Can you confirm that it’s supposed to work now? It’s not working on my end currently.

7

Hi @TimothyVanDyke ,

any news on the release?

Regards,

Sandro

8

Hi Team, apologies for the delay, this should have rolled out completely now. Could I get confirmation on whether the issue is still present?

9

I can confirm that it’s working now. Thanks.