Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Troubleshooting the Constellation SDKs

Updated on November 16, 2022

The following article covers the errors you might encounter when using the Constellation SDKs, the error type, the SDK in which the error occurs, the reason for the error, and the resolution to implement. For more information on troubleshooting Pega Platform-related errors, see Troubleshooting Pega services and Support Guide.

Error code or messageError typeSDKReasonResolution
Application login fails with a Pega login screen displaying instead of the third-party login screenRuntime errorAll

The application displays the Pega login screen instead of the third-party login screen when the iframeLoginUI attribute is set within sdk-config.json.

The error occurs when the application’s top-level portal page uses a different domain than the one configured in the Infinity server and occurs because the browser block’s third-party site cookies. The authentication redirects currently rely on cookies, especially Pega RULES cookie.
Avoid using iframeLoginUI if your top-level page domain is not the same as the one in Infinity server. Alternatively, ensure that the user’s browser does not block third-party cookies.
ERR_CERT_INVALIDRuntime errorAllSelf-signed certificates are either invalid or missing.

Configure a trusted self-signed certificate for localhost.

For more information, see the Setting up a secure self-signed certificate for localhost section in the SDK's Readme.MD file.

Alternatively, resolve this error temporarily by selecting the appropriate option for the browser to trust the local certificate.

ERROR in unable to locate '/Users/arnoj/GithubRepos/DXIL/xyz-sdk/ constellation-core.*.*' globBuild errorAllConstellation files are missing.

Ensure that the constellationjs npm dependency tag, @pega/constellationjs, in the package.json file is correct based on the version of Pega InfinityTM.

For more information, see Verify the Constellation dependency tag section in the Constellation SDK guide.

ERR_SSL_PROTOCOL_ERRORRuntime errorAllThis issue occurs when using the Google Chrome browser and the local front-end server is configured with HTTP. Due to Google Chrome’s domain security policies, the browser automatically redirects to the HTTPS protocol.

Modify Google Chrome’s domain security policies to ignore localhost: 

  1. Close all instances of Google Chrome, and then load chrome://net-internals/#hsts. The Domain Security Policy settings opens.  

  2. Navigate to the Delete domain security policies section. 

  3. Enter localhost in the section’s text box, and then click Delete

  1. (Optional). Clear the browser cache. 

Executable doesn't exist at /Users/...Runtime error8.7 release-based React SDK onlyThis error occurs when you run the application testing commands in a machine that does not have Playwright installed.

Install Playwright and run the test command again. To install Playwright, open a terminal window and execute the following command: 

npx playwright install

GET http://localhost:35729/livereload.js net::ERR_CONNECTION_REFUSED

Runtime error

Web Components only

This error displays in the JavaScript console. 

The webserver you are running is not configured in the "watch" mode. So, code changes, when detected, are not loaded properly. 

The live-reload feature is useful in a development server, you can disable it from the production server. To do so, remove the following livereload.js script from the index.html file located in the src directory:

<script src="http://localhost:35729/livereload.js"></script>

Note: This also disables the application's live-reload. 

Invalid value provided for redirect_uri parameterRuntime errorAllRequested URI is not present in the list of redirect URIs in the OAuth 2.0 client registration records.

Verify and update the list of redirect URIs in the OAuth 2.0 client registration records (Dev Studio > Records > Security > OAuth 2.0 Client Registration). 

For more information, see Verify and update OAuth 2.0 client registration records section in the Constellation SDK guide.

Recurring authentication pop-up windows when running the application in Embedded mode using localhost as the domain when the user is already authenticated.Runtime error8.7 release-based SDKs only

This issue occurs within Chromium-based browsers (such as Chrome and Edge) when the Samesite cookie is not enabled and set to None within the Cross-Site Request Forgery (CSRF) system settings. The SDKs require this setting for silent authentication to properly succeed when the localhost domain is used.

Edit the CSRF settings based on the following steps: 

  1. In the header of Dev Studio, click Configure > System > Settings > Cross-Site Request Forgery
  2. Select the Enable samesite cookie attribute checkbox. 
  3. In the Samesite Options list, select None
  4. Click Submit
  5. OPTIONAL. Restart the server.

For more information, see Enabling and configuring CSRF. 

The Same Origin Policy disallows reading the remote resource at […]Runtime errorAllAllowed Headers and Exposed Headers values are not configured correctly.

Verify that you have all the headers recommended for the SDK (Dev Studio > Records > Security > Cross Origin Resource Sharing).

For more information, see Verify and update CORS record section in the Constellation SDK guide.

Using Constellation version 8.X.X. Ensure this is the same version as your Infinity server.Runtime warningAllIt is required that the ConstellationJS Engine files used in the SDK match the Pega Infinity version that the SDK application is using. The ConstellationJS Engine file version is specified in the value given to the @pega/constellationjs dependency in the package.json file. For example, “SDK-8.7.3”.

This warning is always written to the JS console when the SDK-based application is first loaded.

If the SDK application fails to load after a successful login, the first step should be to verify whether the Constellation dependency tag (@pega/constellationjs) in the package.json file is correct with respect to the version of Pega Infinity you are using.

For example, if using Pega Infinity 8.8, ensure that the value of the Constellation dependency tag is SDK-8.8.0.

If the issue persists, verify whether there are incompatible Constellation files in the constellation folder. Delete the files incompatible with the version of Pega Infinity.

Remove existing node modules and reinstall it if you update the Constellation dependency tag or replace the Constellation files.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us