• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

App Variable Expression Sometimes Not Saveable

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • App Variable Expression Sometimes Not Saveable

    Hello, I have a problem where app expressions sometimes do not save in some cases. The following will run through the steps to reproduce.

    I have an app variable named "testText". I click to open the expression for editing and enter the expression as shown below and have an extra space character at the end of each of the 2 lines:


    image.png
    I click Save and it saves. I click again to open the expression for editing and remove the trailing space on each of the 2 lines. I then click Save and nothing happens. I go to see the logs in the browser developer tools:?

    image.png
    Tested with version 6.3.20250207.0?

  • #2
    Is this app variable linked to something? If so, what is it linked to?

    Comment


    • #3
      The app variable for this example is not linked to anything. Make sure to use double quotes and not single quotes. I tested this again in a new app and it still produces the same issue.

      Comment


      • #4
        Did you paste the code into the NAB editor or type it? I am unable to replicate this using double quotes and a space at the end of each line.

        Comment


        • #5
          I type the expression in. To clarify, saving it with the space at the end of each line works, but if you then bring up the expression again and remove those 2 spaces (or even just one of them) and then attempt to save with the space(s) removed, the expression popup stays up and an error gets logged to the browser's developer console. Thanks for looking into this.

          Comment


          • #6
            I was able to replicate this, and it will be fixed in the next 6.3 update. Thanks!

            Comment

            Working...
            X