[Bug]: Unable to deploy app with Flow extensions

[patryk-smc]

Please confirm that you have:

• Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
• Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?

Extension

Expected behavior

It should deploy.

Actual behavior

I recently started experimenting with Flow extensions and ran into an issue. Initially, I created an extension with a handle longer than 30 characters, unaware of the character limit. I deployed it to my staging environment, which failed, but oddly enough, the app version was released without the extension.

I then shortened the handle and redeployed to staging. Unfortunately, since then, I’ve been encountering errors like the following.

I tried deploying directly from my computer in the staging environment, and it worked fine. I was hopeful that it would now work in CI, but after retrying the release phase, the same error persists.

Next, I deleted the extension folder and redeployed to staging, and everything worked as expected - Flow extension was gone. However, when I reverted the commit that removed the folder, I’m back to encountering the same error.

Verbose output

[redacted]

[isaacroldan]

Hi @patryk-smc, sorry for the delayed response.

This is a known bug when you change the handle of a extension. We are working on improving this.

In the meantime, there is a way to work around this:

• When you do a deploy locally from your machine and it works, you should see that a file called .env.staging is updated. (the name of the .env file is related to the name of your active app.toml file)
• This file contains the UUID of your extensions. If you set the environment variables defined in this file into your CI, the CLI running on CI will be able to automatically match your local extensions with your remote extensions.

Hope this helps!

[patryk-smc]

Hi Isaac, I managed to get this to work by starting over again. But I can tell for sure that Flow extensions don't add UUIDs to env files.

[isaacroldan]

Hi @patryk-smc, after deploying it should update the corresponding .env file, do you see any value at all on that file?
(just tested and it works as expected for me with a Flow Action)

[patryk-smc]

Isaac, in my case, the .env file wasn’t modified (although it worked for other extensions). I managed to get it working, and since I don’t plan on creating any more extensions, I’m closing this issue.