Hello JT,
We've identified what the source of this bug is, which is in the application and not the plug-in. We'll get this resolved for the next release.
We've identified what the source of this bug is, which is in the application and not the plug-in. We'll get this resolved for the next release.
Comment