feat: Display unhandled exceptions from the Controller extension inside the Info Center.

[avasilev-sap]

#4626

Register handlers on the globalThis object for error or promise rejection events. Any error containing in its stack trace the pattern /changes/coding/path/to/ts/or/js file will be displayed. This is a reliable check because all controllers reside in the changes/coding folder inside the adp project.

Testing done:

• Create a controller and a fragment containing a button. The controller throws an exception when the button is clicked. The error is displayed in the Info center.
• When a controller onInit hook throws runtime error or a promise which is rejected the corresponding error is displayed in the info center.

sap.ui.define(
  [
    "sap/ui/core/mvc/ControllerExtension"
  ],
  function (
    ControllerExtension
  ) {
    "use strict";
    return ControllerExtension.extend("adp.v2app.share", {
      onBtnPress: function () {
        throw new Error("Error on press share button");
      },
      override: {
        onInit: function () {
          // throw new Error('Controller initialization error')
          new Promise((_, reject) => {
            setTimeout(() => {
              reject(new Error("Async controller initialization error"));
            }, 1000);
          });
        }
      },
    });
  },
);

[changeset-bot]

🦋 Changeset detected

Latest commit: c1f926e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@sap-ux-private/preview-middleware-client	Patch
@sap-ux/preview-middleware	Patch
@sap-ux/create	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[hyperspace-insights]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

Display Unhandled Controller Extension Errors in the Info Center

New Feature

✨ Adds global error detection for unhandled exceptions and promise rejections originating from Controller Extensions in the Adaptation Project editor. Matching errors are surfaced as error-level messages in the Info Center panel, helping developers quickly identify runtime issues in their controller code.

Errors are identified by checking if the stack trace contains the pattern /changes/coding/<filename>.(js|ts), which reliably targets controller extension files stored in the ADP project's changes/coding folder.

Changes

• packages/preview-middleware-client/src/flp/init.ts: Added CONTROLLER_EXTENSION_PATH_REGEX pattern, extractError helper to retrieve an Error from both ErrorEvent and PromiseRejectionEvent, reportControllerExtensionErrorToInfoCenter handler that filters by stack trace and sends a message to the Info Center, and registerForControllerExtensionErrors which attaches both error and unhandledrejection listeners to globalThis. The registration is called during FLP init when flex settings are present.
• packages/preview-middleware-client/src/messagebundle.properties: Added the CONTROLLER_EXTENSION_UNHANDLED_ERROR_TITLE i18n key used as the Info Center message title.
• packages/preview-middleware-client/test/unit/flp/init.test.ts: Added a registerForControllerExtensionErrors test suite covering: reporting ErrorEvent with a .js stack trace, reporting unhandledrejection with a .ts stack trace, ignoring unrelated errors, ignoring non-Error objects, ignoring undefined errors, and handling errors with an empty message.
• .changeset/twelve-poets-type.md: Added a patch-level changeset entry for @sap-ux-private/preview-middleware-client.

Images and Links

GitHub Issue #4626: Display unhandled exceptions from the Controller extension inside the Info Center

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.20.37

• LLM: anthropic--claude-4.6-sonnet
• Correlation ID: 6cf7330c-f14c-4a21-8564-3dcca3ba6934
• Summary Prompt: Default Prompt
• File Content Strategy: Full file content
• Event Trigger: pull_request.ready_for_review
• Output Template: Default Template
• GithubContextProvider: FEATURE - Display unhandled exceptions from the Controller extension inside the Info Center. #4626

[hyperspace-insights]

The PR introduces a useful feature but has a few correctness issues to address: the global event listeners are never deregistered (creating a leak and potential duplicate-firing across test runs), non-Error promise rejection reasons are silently dropped even when they originate from a controller extension path, and the test suite's afterEach does not clean up the registered listeners, making repeated test executions unreliable.

PR Bot Information

Version: 1.20.37

• LLM: anthropic--claude-4.6-sonnet
• Agent Instructions:
  • AGENTS.md
  • CLAUDE.md
• File Content Strategy: Full file content
• Event Trigger: pull_request.ready_for_review
• Correlation ID: 6cf7330c-f14c-4a21-8564-3dcca3ba6934

[lfindlaysap]

@avasilev-sap, also in your screenshot "Target was not found" should not end with a period and "controller initialization error" is very generic and not phrased as a sentence. Could you show me where I can suggest changes to them as well?

[avasilev-sap]

@avasilev-sap, also in your screenshot "Target was not found" should not end with a period and "controller initialization error" is very generic and not phrased as a sentence. Could you show me where I can suggest changes to them as well?

The "Target was not found" text is from the application itself. It is not localized or set from our codebase. The text is set as a binding,

bindingString: "{_templPrivGlobal>/generic/messagePage/text}"
oValue: "Target was not found."

You can contact sb from the UI5/RTA team if you want to change the translation.

The second text "controller initialization error" is a dummy text which i used to throw as an exception from a dummy controller just to test the feature. In the Testing done section of this PR there is a small Controller which throws the latter exception. This text is not part of the project, please ignore it.

[Jimmy-Joseph19]

Changes looks good.
Covered with unit test
Changeset found
Ran the branch against integration test result - Paased
https://github.com/SAP/open-ux-tools/actions/runs/25503795851
Did not test locally

[IvoSG]

Changes looks good.
Good test coverage
Changeset is ok
Did not test locally

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
96.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud