`boost-support-ticket.txt`

38 lines
To: support@boostcommerce.net
From: steve@designerwallcoverings.com
Subject: Production shop receiving STAGING API config in Boost app embed — designer-laboratory-sandbox.myshopify.com

Hi Boost team,

We found a serious misconfiguration affecting our production store and want it fixed on your side.

STORE: designer-laboratory-sandbox.myshopify.com (this IS our live production store, serving www.designerwallcoverings.com)
APP: Boost AI Search & Filter v3 (boost-sd), app version 4.8.0, boostThemeLib "default" v2.1.17
LIVE THEME ID: 144076931123

THE PROBLEM
Your app-embed config snippet ("app snippet: config", rendered before </body>) hardcodes the boostSDAppConfig.api block to your STAGING endpoints on every page load of our production storefront:

  filterUrl:     https://staging.bc-solutions.net/bc-sf-filter/filter
  searchUrl:     https://staging.bc-solutions.net/bc-sf-filter/search
  suggestionUrl: https://staging.bc-solutions.net/bc-sf-filter/search/suggest
  productsUrl:   https://staging.bc-solutions.net/bc-sf-filter/search/products
  recommendUrl:  https://staging.bc-solutions.net/discovery/recommend
  cdn:           https://boost-cdn-staging.bc-solutions.net

Those staging endpoints return 403 Forbidden for our shop. Your production endpoints (services.mybcapps.com/bc-sf-filter/...) serve our index correctly (75,278 products with a full filter tree).

The snippet DOES contain the env === 'production' self-correction (our theme ID 144076931123 is registered env:"production" in the themeInfo map, and the Object.assign to the mybcapps production URLs is present). However, the snippet's final merge — window.boostSDAppConfig = merge(boostSDAppConfig, window.boostSDAppConfig) — lets any pre-existing window config keys win, so under some runtime conditions the staging api block takes precedence. We received a customer complaint (empty filter dropdowns, search results page returning nothing, broken infinite scroll) that matches the staging path winning intermittently.

WHAT WE NEED
Please fix the embed generation for our shop so the emitted config contains PRODUCTION api URLs directly (no staging literals in the snippet at all), rather than relying on the runtime self-correction. A production shop should never ship staging endpoints in its page source.

We have deployed a defensive theme-side interceptor that rewrites staging.bc-solutions.net values to your production endpoints at runtime, so our storefront is currently stable — but the staging block is still in every page load and we'd like the root cause corrected.

Happy to provide HAR files or anything else you need.

Thanks,
Steve Abrams
Designer Wallcoverings and Fabrics
steve@designerwallcoverings.com | (888) 373-4564