Internal Errors During “MAKE IT LIVE” Mission Validation (App ID: 1377ED72-4E26-4022-8166-75AF5C6E6E2B)

Backendless Version

6.x (Online)

Client SDK

UI Builder (JavaScript)

Application ID

1377ED72-4E26-4022-8166-75AF5C6E6E2B


Expected Behavior

A new developer on our team is completing the UI Builder Starter Pack → MAKE IT LIVE! mission.
Steps expected to work normally:

  1. Open mission “Add Print to the On Page Enter Event and Run the Page.”
  2. Add print("Hello World!") (or equivalent) to the On Page Enter event.
  3. Click Validate Task and proceed to the next mission step once validation succeeds.

Actual Behavior

The mission fails validation every time, even though the code runs correctly and prints to the console.
Error messages displayed:

  • Oops. An internal error [5080cc5c-f9b6-411b-8687-cec857120d61] has occurred. We are working on it. Please try again later.
  • Similar errors occur on step 2 (“Add Print to the On Scroll Event and Run the Page”).
  • “Validation Error” message appears below the mission window.
  • Mission progress remains stuck at 1/3.

The browser console shows successful execution of the print statement (Hello World! logged) but the validation step always fails.

Screenshots of the error dialogs and console output are attached.




Reproducible Test Case

Steps to reproduce (in a clean account or project):

  1. Open the UI Builder Starter Pack missions.
  2. Start MAKE IT LIVE! → Add Print to the On Page Enter Event and Run the Page.
  3. Add a simple print statement and click Validate Task.
  4. Observe the internal error popup and validation failure.

Additional Notes

  • Tested on Chrome and Edge, cleared cache, and restarted the mission multiple times.
  • Occurs for a new user account being onboarded to our organization.
  • The mission environment appears to run, but Backendless validation throws an internal error each time.

Hi @Andreas_Marinopoulos

I checked the logs — these errors occur because the validation request didn’t include the required cookies, and the server responded with:

“Unfortunately, we were unable to identify your developer account. This issue may have occurred because a necessary cookie was blocked. Please ensure that your browser is set to allow third-party cookies. You can typically find this setting in your browser’s ‘Privacy and Security’ configuration screen.”

Overall, the mission validation definitely works — I tested it myself on both an old and a new account, and everything worked fine with no errors.
Also, this issue isn’t related to the developer being from your organization — it’s entirely due to the specific browser settings of the developer.

Regards,
Viktor

Thanks Victor, should she try a different browser or simply allow cookies?

Hi Andreas, allowing cookies should do it. But you are welcome to try a different browser too.

Regards,
Mark