Troubleshooting

Cause. The environment file has not been generated.

Fix.

This is the single most common first-run failure. See environments.

Cause. Same root cause, hit from the production build path — angular.json’s `production configuration replaces environment.ts with environment.prod.ts, which set-env.ts writes only when ENV_NAME=release.

Fix. Run setenv.sh (with release if you genuinely want a production build).

Cause. Node/CLI version mismatch, usually after switching Node versions.

Fix.

If that does not help, reinstall the CLI:

The README documents a workaround for stubborn uninstalls: switch to an older Node (nvm use v8.11.3), uninstall, switch back, reinstall.

Fix. Check Node and npm versions first, then:

Cause. AOT compiling ~420 components exceeds Node’s default heap.

Fix. Use the high-memory scripts rather than plain ng build:

CI uses 12288 (deployment/build.sh). See build and deployment.

Cause. generate_gci.py computes the workflow GCI for non-release environments.

Fix. Install Python 3. Only ENV_NAME=release skips this step.

Cause. husky install runs in postinstall; it is skipped if npm install was run with --ignore-scripts.

Fix. npm run init:husky.

Cause. You are serving on a port that is not registered with the Google client.

Fix. Use one of 4200, 4300, 4400, 4500, 4600, 5000, 8082 — and remember 4600 is EVA’s dev port. See local development.

Cause. Wrong backend, or the backend is down. LoginComponent maps other statuses distinctly: 401 → "Invalid login or password", 403 → "Access denied".

Fix. Check which environment you configured (./deployment/checkenv.sh) and whether that backend is up.

Cause. The Google credential was absent from the callback payload — AuthEffects.authLoginGoogle guards against Google changing its response shape.

Fix. Check for a Google Identity Services change and for third-party-cookie or tracking-prevention settings blocking the flow.

Causes.

There is no token refresh. See authentication.

Cause. sessionStorage['loginRedirectUrl'] is set by RouteAccessResolver and never cleared after use, so a stale value can survive.

Fix. Clear sessionStorage for the origin.

Expected. Stated in the README. The app depends on localStorage, sessionStorage and a cross-subdomain cookie.

Cause. supplier.suppliers[supplierKey] caches every supplier visited this session and nothing invalidates it.

Fix. Trigger a refresh (FetchSupplierDetails({ supplierKey, refresh: true }) — which also appends refreshTimestamp to bust any HTTP cache), or reload the page. See suppliers.

Cause. UsersService.getPreparedCombinedList() caches users and groups in a BehaviorSubject for the whole session, with no invalidation.

Fix. Reload. See caching and persistence.

Expected. With no persisted query, the default is created_since:<today − 1 day>. Change the query; it is persisted to localStorage['suppliers_last_query'].

Cause. The utils slice is cached in localStorage via lscache with a 24-hour TTL.

Fix. Dispatch FetchUtilAttribute with refresh, or clear the lscache-utilsState key.

Cause. On the balance-approval screen, a non-zero short_to_long_mov_avg_ratio_rcv silently overwrites short_to_long_mov_avg_ratio. See balance approval.

Cause. Global settings beat build flags — the resolved set is seeded from the FEATURE_FLAGS_IA global setting, not from environment.featureFlags.

Fix. Enable it at /admin/feature-flags (needs DEV) and save to global settings, or set a session override.

Cause. Someone saved to global settings, which stamps a newer lastChange than your stored session timestamp — and session overrides older than the setting are discarded.

Fix. Re-apply them. See feature flags.

Cause. isEnabled reads build flags plus sessionStorage only. It is correct after FeatureFlagsGeneralGuard has run initFF() on a guarded navigation. Calling it from a constructor that runs earlier (as AppComponent does for CHECK_VPN) can read false on a cold load.

Fix. Move the check later in the lifecycle, or into a guard.

Expected. appEnabledByFeatureFlag evaluates once, in its input setter. Reload.

Expected for flags applied only in the sidebar. FeatureFlagsGeneralGuard always passes; only FeatureFlagGuard (used on two routes) redirects to /404.

Check, in order.

See authorisation.

Cause. SubPermissionsGuard — the route requires one of data.requireOneOfSubPermissions and the user has none. It also denies when the route data is missing or empty.

Expected. AppComponent adds a restricted-access class to document.body, which SCSS uses to hide UI wholesale, and the supplier aggregate load skips several calls for ADVANCE_AUDITORS.

Check.

See iframe messaging and EVA.

Cause. Local and deployed differ in where the token lives — query parameter versus cookie — and origin checks always allow localhost on non-production builds.

Cause. ResizeIframeService.getElement throws 'Element not found!' when the target frame is gone, and the throw terminates the incomingMessage$ subscription — so all subsequent resize handling stops.

Fix. Reload.

Expected. CommunicationService.setDomain() assigns document.domain before every send, wrapped in an empty catch. The API is deprecated in modern browsers.

Cause. SseService propagates any onerror or JSON parse failure as an observable error, which terminates the stream. There is no reconnect.

Fix. Reload to re-open the stream. See real-time streams.

Cause. B2bWorkflowService.subscribeTask creates a new inner subscription per received message and never tears them down.

Fix. Subscribe to taskMonitoring() directly and filter yourself.

Expected. :supKey is declared before approval in the /processes table, so the URL matches PendingEditComponent.

Fix. Use /proceses/approval — one s. See processes.

Expected. PendingInterceptorService toasts any 5xx, and the calling service or component toasts as well. PaymentBatchRepositoryService adds its own message per operation. See error handling.

Cause. CardManagementService.getCards sends the provider filter as a body on a GET request, which some proxies drop.

See card programmes.

Cause. Karma runs with jasmine.random: false and ng-bullet’s `configureTestSuite shares the TestBed across a suite. A spec that writes to localStorage/sessionStorage, or sets cerialize casing via DeserializeKeysFrom/SerializeKeysTo, leaks into the next.

Fix. Clean up in afterEach. See testing.

Cause. karma.conf.js sets CHROME_BIN from Puppeteer’s bundled binary.

Fix. Reinstall so the Puppeteer download completes (npm install), or set CHROME_BIN yourself.

Cause. npm run test:ci is commented out of buildspec.yml. Only buildspec-ci.yml runs the unit suite, as a separate pipeline.

Cause. cypress/support/commands.js imports from application source (AMAZON_SELLER_CENTRAL_MARKETPLACE_KEY, AMAZON_SELLER_CENTRAL). The suite is also marked unmaintained.