Forge Invocation Token's "app.version" property returns unexpected result

Forge
,
1

We are using Remote Backend and Custom UI in our Forge application. After validating and decoding forge invocation token at remote backend, the “app.version” property returns unexpected value.

For example, my site has version 106.2.0 of the installed app, but in this case the “app.version” property returns “3”.

2

Hi @HseyinErbayraktar,
Thanks for reporting this and apologies for the inconvenience. There is a bug and we have created a ticket to track this: https://jira.atlassian.com/browse/ECO-697.

2 Likes
3

Hi @HseyinErbayraktar,
Sorry about the delay. I’d like to inform you that the fix has been deployed, we are now including a new claim called appVersion which will be specifically for the version of the app. version was referring to the version of the module, which is not commonly used and will be deprecated soon. We will be updating the documentation to reflect this shortly as well.

2 Likes