Fixing the share footer logo display issue

The situation

A public share page was not displaying the correct logo due to an error on the path. The live app already used the exact logo successfully. A local edit created a path that pointed to an error. The goal was to make every public share footer show the exact logo used in the app. The share footer named a logo path, but the live app returned an error for it, so recipients did not see the requested logo. The local logo matched the marketing logo, but serving a second copy would add code and deployment without improving the result.

What they weighed

• Serve the local logo at the brand path from the app

• Point share attribution at the external logo URL

• Keep text-only attribution and document the logo as a future enhancement

What they decided

Restore the generic mark to the already-live logo URL

Why

The public share page already used the exact logo successfully. The local path pointed to an error, and serving a second copy would add code and deployment without improving the result. The live share footer already served the exact logo from the canonical marketing URL. The local edit created an error if merged.

The first step

Restore the logo URL, update the generic-share assertion, verify the public share and logo response, then merge and deploy the source correction

How they would know it worked

Every public share footer renders the logo; its image URL returns a successful response, and no share page points to the error path

How it turned out

Not known yet. The result is added here when it comes in.