Loading app version etc. after trapeze was executed

While implementing Trapeze for our Appflow pipeline we noticed an issue which was coming up when you used it in combination with the LiveUpdate Plugin.

We were using trapeze to set the app version, while the build was running. This caused an issue, because the used version of the LiveUpdate Plugin, was the version that was present at the start of the build and not the version we configured in trapeze.

This might be intended, but internally we were discusing if appflow couldn’t just reload the data after executing trapeze. Maybe via setting a flag or by default.

What are you guys thinking about this?