Authenticated Preview resolves valid PNG asset to stale legacy URL

[admin86proof]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Begin V001C‑VR‑R2‑P — FlutterFlow Runtime Asset Resolution Evidence Audit

PROJECT

Final Dashboard 86Proof MVP 3

REQUIRED FLUTTERFLOW HEAD

eS7pVCNnqPxNnOzbvg5Y

REQUIRED BACKEND CHECKPOINT

20260728193318_secure_upload_job_lifecycle_foundation

BACKGROUND

V001C‑VR‑R1 confirmed:

• The authoritative Chef Proof artwork is valid.
• Chef_Proof_Command_Center.png is a standards-compliant PNG.
• Dimensions: 1122×1402
• Color: 8-bit RGB, sRGB
• Encoding: non-interlaced
• Multiple local decoders succeeded.
• FlutterFlow Media Assets successfully registered and decoded the file.
• The Media Assets thumbnail decoded correctly.
• Decoded pixel hashes matched the authoritative artwork exactly.
• Filename punctuation was not the primary cause.
• Authenticated runtime Preview still reported:
  EncodingError: The source image cannot be decoded.

The original Chef image binding was restored after the repaired asset failed in runtime Preview.

Current project history:

• vNs8uLxxXp2IW8lp8Z5Q — repaired asset binding
• eS7pVCNnqPxNnOzbvg5Y — original binding restored

The repaired asset remains registered in Media Assets. Its deletion is not authorized.

PURPOSE

Perform a strictly read-only transport and resolution audit to determine what FlutterFlow authenticated runtime Preview actually requests and receives for the Chef Proof artwork.

Do not attempt another repair, conversion, upload, binding, filename, format, cache workaround or page modification.

PREFLIGHT

Confirm:

1. Local and server heads equal eS7pVCNnqPxNnOzbvg5Y.
2. Workspace is clean.
3. flutterflow ai test passes.
4. Backend checkpoint equals 20260728193318_secure_upload_job_lifecycle_foundation.
5. The V001C‑VR Command Center restoration remains present.
6. /commandCenterDashboard remains requireAuth: true.
7. The original Chef artwork binding is currently restored.
8. Chef_Proof_Command_Center.png remains registered in Media Assets.
9. No work occurred after V001C‑VR‑R1.
10. No Queue or Edge Function work has started.

Stop without changes if the checkpoints differ or the workspace is dirty.

READ-ONLY AUDIT

Inspect the current project, FlutterFlow history, generated asset records, prior runtime evidence and available authenticated Preview network evidence.

Do not check out or restore an older project revision.

Determine for both assets:

• Original:
  ChatGPT_Image_Jun_14,_2026_at_11_12_18_AM.png
• Repaired:
  Chef_Proof_Command_Center.png

Report:

1. FlutterFlow asset identifier

2. Registered source path or logical asset key

3. Generated runtime reference

4. Exact request destination category:

   • Packaged application asset
   • FlutterFlow Media Asset
   • Legacy FlutterFlow Storage
   • Firebase Storage
   • Signed remote URL
   • Other

5. HTTP status

6. Redirect chain

7. Response Content-Type

8. Response length

9. First-byte/file-signature classification

10. Whether the response is:

    • Valid PNG bytes
    • XML error document
    • HTML error document
    • JSON response
    • Empty body
    • Truncated image
    • Other

11. Whether the URL references the new safe filename or a stale legacy location

12. Whether the runtime binding uses the same asset record decoded by Media Assets

13. Whether URL encoding, authorization, cache metadata, service-worker state or asset-manifest state differs between Media Assets and authenticated Preview

14. Whether Preview returns an error payload with a misleading or missing image content type

15. Exact console error source and widget association

For response comparison, record SHA-256 hashes where bytes are safely available.

Do not expose:

• Authentication tokens
• Signed query parameters
• Cookies
• Session identifiers
• Private Storage paths
• User identifiers

Redact sensitive URL portions in the final report.

HISTORICAL REVISION INSPECTION

Read-only inspect revision:

vNs8uLxxXp2IW8lp8Z5Q

Determine:

• Whether Image_tgel0w5i referenced the correct new asset identifier
• Whether generated code referenced Chef_Proof_Command_Center.png
• Whether it instead resolved to the old asset record or legacy path
• Whether the registered asset existed in the runtime manifest/package
• Whether the failure occurred before or after Flutter’s image decoder received the payload

Do not restore, apply, check out or rebind this revision.

If evidence from the failed revision is unavailable, report the limitation. Do not recreate the failure by modifying the current page.

COMPARATIVE CONTROL CHECK

Use the working assets only as read-only controls:

• 86_Proof_Logo_Background_Removed.png
• Command_Center_Hero_Original.png

Compare their successful runtime resolution with the failing Chef asset resolution:

• Asset-record structure
• Runtime reference type
• Request destination
• Status
• Content type
• File signature
• Manifest presence
• Cache behavior

Do not modify either working asset.

CLASSIFICATION

Classify the blocker as one of:

• Stale FlutterFlow asset binding or manifest reference
• Authenticated Preview authorization failure
• Legacy Storage resolution failure
• Runtime asset packaging failure
• Browser/service-worker cache mismatch
• Registered asset-record corruption
• FlutterFlow platform defect
• Unable to determine

Clearly separate confirmed facts from inference.

SUPPORT EVIDENCE

Determine whether the evidence is sufficient for a FlutterFlow Support escalation.

If sufficient, prepare a concise support-ready incident summary containing:

• Project name
• Affected page and widget
• Current FlutterFlow head
• Failed historical binding revision
• Asset filenames
• Successful local and Media Assets decoding
• Authenticated Preview failure
• Sanitized request/response evidence
• Reproduction steps
• Expected result
• Actual result
• Confirmation that two other page assets render correctly
• Confirmation that the error persists with a valid newly registered PNG
• Confirmation that no backend or authentication mutation is involved

Do not submit the support request.

PROHIBITED ACTIONS

Do not:

• Modify any FlutterFlow object
• Change an image binding
• Upload or register another asset
• Delete either asset
• Rename an asset
• Re-encode the artwork again
• Try WebP, JPG, SVG or another PNG
• Clear or change project data
• Change authentication
• Change routes
• Change Storage
• Change Supabase
• Change the Command Center layout
• Commit anything
• Run the unfinished viewport, hard-refresh or navigation-return closure tests
• Close V001C‑VR

FINAL REPORT

Report:

• Preflight result
• Starting and final FlutterFlow heads
• Starting and final backend checkpoints
• Workspace status
• Original asset resolution path and response classification
• Repaired asset resolution path and response classification
• Working logo and hero control results
• Media Assets versus authenticated Preview comparison
• Historical binding inspection result
• Exact confirmed failure layer
• Whether the image decoder received PNG bytes or an error payload
• Whether a stale legacy path remained involved
• Whether cache or service-worker behavior is implicated
• Sanitized reproduction steps
• Recommended next action
• Support-ready incident summary
• Any evidence still missing
• Confirmation that no project, asset, page, component, route, authentication, Supabase, Storage, Queue, Edge Function or application-data change occurred
• Confirmation that no commit was created
• Confirmation that V001C‑VR remains open

Stop after reporting V001C‑VR‑R2‑P.

Expected Behavior

Begin V001C‑VR‑R2‑P — FlutterFlow Runtime Asset Resolution Evidence Audit

PROJECT

Final Dashboard 86Proof MVP 3

REQUIRED FLUTTERFLOW HEAD

eS7pVCNnqPxNnOzbvg5Y

REQUIRED BACKEND CHECKPOINT

20260728193318_secure_upload_job_lifecycle_foundation

BACKGROUND

V001C‑VR‑R1 confirmed:

• The authoritative Chef Proof artwork is valid.
• Chef_Proof_Command_Center.png is a standards-compliant PNG.
• Dimensions: 1122×1402
• Color: 8-bit RGB, sRGB
• Encoding: non-interlaced
• Multiple local decoders succeeded.
• FlutterFlow Media Assets successfully registered and decoded the file.
• The Media Assets thumbnail decoded correctly.
• Decoded pixel hashes matched the authoritative artwork exactly.
• Filename punctuation was not the primary cause.
• Authenticated runtime Preview still reported:
  EncodingError: The source image cannot be decoded.

The original Chef image binding was restored after the repaired asset failed in runtime Preview.

Current project history:

• vNs8uLxxXp2IW8lp8Z5Q — repaired asset binding
• eS7pVCNnqPxNnOzbvg5Y — original binding restored

The repaired asset remains registered in Media Assets. Its deletion is not authorized.

PURPOSE

Perform a strictly read-only transport and resolution audit to determine what FlutterFlow authenticated runtime Preview actually requests and receives for the Chef Proof artwork.

Do not attempt another repair, conversion, upload, binding, filename, format, cache workaround or page modification.

PREFLIGHT

Confirm:

1. Local and server heads equal eS7pVCNnqPxNnOzbvg5Y.
2. Workspace is clean.
3. flutterflow ai test passes.
4. Backend checkpoint equals 20260728193318_secure_upload_job_lifecycle_foundation.
5. The V001C‑VR Command Center restoration remains present.
6. /commandCenterDashboard remains requireAuth: true.
7. The original Chef artwork binding is currently restored.
8. Chef_Proof_Command_Center.png remains registered in Media Assets.
9. No work occurred after V001C‑VR‑R1.
10. No Queue or Edge Function work has started.

Stop without changes if the checkpoints differ or the workspace is dirty.

READ-ONLY AUDIT

Inspect the current project, FlutterFlow history, generated asset records, prior runtime evidence and available authenticated Preview network evidence.

Do not check out or restore an older project revision.

Determine for both assets:

• Original:
  ChatGPT_Image_Jun_14,_2026_at_11_12_18_AM.png
• Repaired:
  Chef_Proof_Command_Center.png

Report:

1. FlutterFlow asset identifier

2. Registered source path or logical asset key

3. Generated runtime reference

4. Exact request destination category:

   • Packaged application asset
   • FlutterFlow Media Asset
   • Legacy FlutterFlow Storage
   • Firebase Storage
   • Signed remote URL
   • Other

5. HTTP status

6. Redirect chain

7. Response Content-Type

8. Response length

9. First-byte/file-signature classification

10. Whether the response is:

    • Valid PNG bytes
    • XML error document
    • HTML error document
    • JSON response
    • Empty body
    • Truncated image
    • Other

11. Whether the URL references the new safe filename or a stale legacy location

12. Whether the runtime binding uses the same asset record decoded by Media Assets

13. Whether URL encoding, authorization, cache metadata, service-worker state or asset-manifest state differs between Media Assets and authenticated Preview

14. Whether Preview returns an error payload with a misleading or missing image content type

15. Exact console error source and widget association

For response comparison, record SHA-256 hashes where bytes are safely available.

Do not expose:

• Authentication tokens
• Signed query parameters
• Cookies
• Session identifiers
• Private Storage paths
• User identifiers

Redact sensitive URL portions in the final report.

HISTORICAL REVISION INSPECTION

Read-only inspect revision:

vNs8uLxxXp2IW8lp8Z5Q

Determine:

• Whether Image_tgel0w5i referenced the correct new asset identifier
• Whether generated code referenced Chef_Proof_Command_Center.png
• Whether it instead resolved to the old asset record or legacy path
• Whether the registered asset existed in the runtime manifest/package
• Whether the failure occurred before or after Flutter’s image decoder received the payload

Do not restore, apply, check out or rebind this revision.

If evidence from the failed revision is unavailable, report the limitation. Do not recreate the failure by modifying the current page.

COMPARATIVE CONTROL CHECK

Use the working assets only as read-only controls:

• 86_Proof_Logo_Background_Removed.png
• Command_Center_Hero_Original.png

Compare their successful runtime resolution with the failing Chef asset resolution:

• Asset-record structure
• Runtime reference type
• Request destination
• Status
• Content type
• File signature
• Manifest presence
• Cache behavior

Do not modify either working asset.

CLASSIFICATION

Classify the blocker as one of:

• Stale FlutterFlow asset binding or manifest reference
• Authenticated Preview authorization failure
• Legacy Storage resolution failure
• Runtime asset packaging failure
• Browser/service-worker cache mismatch
• Registered asset-record corruption
• FlutterFlow platform defect
• Unable to determine

Clearly separate confirmed facts from inference.

SUPPORT EVIDENCE

Determine whether the evidence is sufficient for a FlutterFlow Support escalation.

If sufficient, prepare a concise support-ready incident summary containing:

• Project name
• Affected page and widget
• Current FlutterFlow head
• Failed historical binding revision
• Asset filenames
• Successful local and Media Assets decoding
• Authenticated Preview failure
• Sanitized request/response evidence
• Reproduction steps
• Expected result
• Actual result
• Confirmation that two other page assets render correctly
• Confirmation that the error persists with a valid newly registered PNG
• Confirmation that no backend or authentication mutation is involved

Do not submit the support request.

PROHIBITED ACTIONS

Do not:

• Modify any FlutterFlow object
• Change an image binding
• Upload or register another asset
• Delete either asset
• Rename an asset
• Re-encode the artwork again
• Try WebP, JPG, SVG or another PNG
• Clear or change project data
• Change authentication
• Change routes
• Change Storage
• Change Supabase
• Change the Command Center layout
• Commit anything
• Run the unfinished viewport, hard-refresh or navigation-return closure tests
• Close V001C‑VR

FINAL REPORT

Report:

• Preflight result
• Starting and final FlutterFlow heads
• Starting and final backend checkpoints
• Workspace status
• Original asset resolution path and response classification
• Repaired asset resolution path and response classification
• Working logo and hero control results
• Media Assets versus authenticated Preview comparison
• Historical binding inspection result
• Exact confirmed failure layer
• Whether the image decoder received PNG bytes or an error payload
• Whether a stale legacy path remained involved
• Whether cache or service-worker behavior is implicated
• Sanitized reproduction steps
• Recommended next action
• Support-ready incident summary
• Any evidence still missing
• Confirmation that no project, asset, page, component, route, authentication, Supabase, Storage, Queue, Edge Function or application-data change occurred
• Confirmation that no commit was created
• Confirmation that V001C‑VR remains open

Stop after reporting V001C‑VR‑R2‑P.

Steps to Reproduce

Begin V001C‑VR‑R2‑P — FlutterFlow Runtime Asset Resolution Evidence Audit

PROJECT

Final Dashboard 86Proof MVP 3

REQUIRED FLUTTERFLOW HEAD

eS7pVCNnqPxNnOzbvg5Y

REQUIRED BACKEND CHECKPOINT

20260728193318_secure_upload_job_lifecycle_foundation

BACKGROUND

V001C‑VR‑R1 confirmed:

• The authoritative Chef Proof artwork is valid.
• Chef_Proof_Command_Center.png is a standards-compliant PNG.
• Dimensions: 1122×1402
• Color: 8-bit RGB, sRGB
• Encoding: non-interlaced
• Multiple local decoders succeeded.
• FlutterFlow Media Assets successfully registered and decoded the file.
• The Media Assets thumbnail decoded correctly.
• Decoded pixel hashes matched the authoritative artwork exactly.
• Filename punctuation was not the primary cause.
• Authenticated runtime Preview still reported:
  EncodingError: The source image cannot be decoded.

The original Chef image binding was restored after the repaired asset failed in runtime Preview.

Current project history:

• vNs8uLxxXp2IW8lp8Z5Q — repaired asset binding
• eS7pVCNnqPxNnOzbvg5Y — original binding restored

The repaired asset remains registered in Media Assets. Its deletion is not authorized.

PURPOSE

Perform a strictly read-only transport and resolution audit to determine what FlutterFlow authenticated runtime Preview actually requests and receives for the Chef Proof artwork.

Do not attempt another repair, conversion, upload, binding, filename, format, cache workaround or page modification.

PREFLIGHT

Confirm:

1. Local and server heads equal eS7pVCNnqPxNnOzbvg5Y.
2. Workspace is clean.
3. flutterflow ai test passes.
4. Backend checkpoint equals 20260728193318_secure_upload_job_lifecycle_foundation.
5. The V001C‑VR Command Center restoration remains present.
6. /commandCenterDashboard remains requireAuth: true.
7. The original Chef artwork binding is currently restored.
8. Chef_Proof_Command_Center.png remains registered in Media Assets.
9. No work occurred after V001C‑VR‑R1.
10. No Queue or Edge Function work has started.

Stop without changes if the checkpoints differ or the workspace is dirty.

READ-ONLY AUDIT

Inspect the current project, FlutterFlow history, generated asset records, prior runtime evidence and available authenticated Preview network evidence.

Do not check out or restore an older project revision.

Determine for both assets:

• Original:
  ChatGPT_Image_Jun_14,_2026_at_11_12_18_AM.png
• Repaired:
  Chef_Proof_Command_Center.png

Report:

1. FlutterFlow asset identifier

2. Registered source path or logical asset key

3. Generated runtime reference

4. Exact request destination category:

   • Packaged application asset
   • FlutterFlow Media Asset
   • Legacy FlutterFlow Storage
   • Firebase Storage
   • Signed remote URL
   • Other

5. HTTP status

6. Redirect chain

7. Response Content-Type

8. Response length

9. First-byte/file-signature classification

10. Whether the response is:

    • Valid PNG bytes
    • XML error document
    • HTML error document
    • JSON response
    • Empty body
    • Truncated image
    • Other

11. Whether the URL references the new safe filename or a stale legacy location

12. Whether the runtime binding uses the same asset record decoded by Media Assets

13. Whether URL encoding, authorization, cache metadata, service-worker state or asset-manifest state differs between Media Assets and authenticated Preview

14. Whether Preview returns an error payload with a misleading or missing image content type

15. Exact console error source and widget association

For response comparison, record SHA-256 hashes where bytes are safely available.

Do not expose:

• Authentication tokens
• Signed query parameters
• Cookies
• Session identifiers
• Private Storage paths
• User identifiers

Redact sensitive URL portions in the final report.

HISTORICAL REVISION INSPECTION

Read-only inspect revision:

vNs8uLxxXp2IW8lp8Z5Q

Determine:

• Whether Image_tgel0w5i referenced the correct new asset identifier
• Whether generated code referenced Chef_Proof_Command_Center.png
• Whether it instead resolved to the old asset record or legacy path
• Whether the registered asset existed in the runtime manifest/package
• Whether the failure occurred before or after Flutter’s image decoder received the payload

Do not restore, apply, check out or rebind this revision.

If evidence from the failed revision is unavailable, report the limitation. Do not recreate the failure by modifying the current page.

COMPARATIVE CONTROL CHECK

Use the working assets only as read-only controls:

• 86_Proof_Logo_Background_Removed.png
• Command_Center_Hero_Original.png

Compare their successful runtime resolution with the failing Chef asset resolution:

• Asset-record structure
• Runtime reference type
• Request destination
• Status
• Content type
• File signature
• Manifest presence
• Cache behavior

Do not modify either working asset.

CLASSIFICATION

Classify the blocker as one of:

• Stale FlutterFlow asset binding or manifest reference
• Authenticated Preview authorization failure
• Legacy Storage resolution failure
• Runtime asset packaging failure
• Browser/service-worker cache mismatch
• Registered asset-record corruption
• FlutterFlow platform defect
• Unable to determine

Clearly separate confirmed facts from inference.

SUPPORT EVIDENCE

Determine whether the evidence is sufficient for a FlutterFlow Support escalation.

If sufficient, prepare a concise support-ready incident summary containing:

• Project name
• Affected page and widget
• Current FlutterFlow head
• Failed historical binding revision
• Asset filenames
• Successful local and Media Assets decoding
• Authenticated Preview failure
• Sanitized request/response evidence
• Reproduction steps
• Expected result
• Actual result
• Confirmation that two other page assets render correctly
• Confirmation that the error persists with a valid newly registered PNG
• Confirmation that no backend or authentication mutation is involved

Do not submit the support request.

PROHIBITED ACTIONS

Do not:

• Modify any FlutterFlow object
• Change an image binding
• Upload or register another asset
• Delete either asset
• Rename an asset
• Re-encode the artwork again
• Try WebP, JPG, SVG or another PNG
• Clear or change project data
• Change authentication
• Change routes
• Change Storage
• Change Supabase
• Change the Command Center layout
• Commit anything
• Run the unfinished viewport, hard-refresh or navigation-return closure tests
• Close V001C‑VR

FINAL REPORT

Report:

• Preflight result
• Starting and final FlutterFlow heads
• Starting and final backend checkpoints
• Workspace status
• Original asset resolution path and response classification
• Repaired asset resolution path and response classification
• Working logo and hero control results
• Media Assets versus authenticated Preview comparison
• Historical binding inspection result
• Exact confirmed failure layer
• Whether the image decoder received PNG bytes or an error payload
• Whether a stale legacy path remained involved
• Whether cache or service-worker behavior is implicated
• Sanitized reproduction steps
• Recommended next action
• Support-ready incident summary
• Any evidence still missing
• Confirmation that no project, asset, page, component, route, authentication, Supabase, Storage, Queue, Edge Function or application-data change occurred
• Confirmation that no commit was created
• Confirmation that V001C‑VR remains open

Stop after reporting V001C‑VR‑R2‑P.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

Begin V001C‑VR‑R2‑P — FlutterFlow Runtime Asset Resolution Evidence Audit PROJECT Final Dashboard 86Proof MVP 3 REQUIRED FLUTTERFLOW HEAD eS7pVCNnqPxNnOzbvg5Y REQUIRED BACKEND CHECKPOINT 20260728193318_secure_upload_job_lifecycle_foundation BACKGROUND V001C‑VR‑R1 confirmed: * The authoritative Chef Proof artwork is valid. * Chef_Proof_Command_Center.png is a standards-compliant PNG. * Dimensions: 1122×1402 * Color: 8-bit RGB, sRGB * Encoding: non-interlaced * Multiple local decoders succeeded. * FlutterFlow Media Assets successfully registered and decoded the file. * The Media Assets thumbnail decoded correctly. * Decoded pixel hashes matched the authoritative artwork exactly. * Filename punctuation was not the primary cause. * Authenticated runtime Preview still reported: EncodingError: The source image cannot be decoded. The original Chef image binding was restored after the repaired asset failed in runtime Preview. Current project history: * vNs8uLxxXp2IW8lp8Z5Q — repaired asset binding * eS7pVCNnqPxNnOzbvg5Y — original binding restored The repaired asset remains registered in Media Assets. Its deletion is not authorized. PURPOSE Perform a strictly read-only transport and resolution audit to determine what FlutterFlow authenticated runtime Preview actually requests and receives for the Chef Proof artwork. Do not attempt another repair, conversion, upload, binding, filename, format, cache workaround or page modification. PREFLIGHT Confirm: 1. Local and server heads equal eS7pVCNnqPxNnOzbvg5Y. 2. Workspace is clean. 3. flutterflow ai test passes. 4. Backend checkpoint equals 20260728193318_secure_upload_job_lifecycle_foundation. 5. The V001C‑VR Command Center restoration remains present. 6. /commandCenterDashboard remains requireAuth: true. 7. The original Chef artwork binding is currently restored. 8. Chef_Proof_Command_Center.png remains registered in Media Assets. 9. No work occurred after V001C‑VR‑R1. 10. No Queue or Edge Function work has started. Stop without changes if the checkpoints differ or the workspace is dirty. READ-ONLY AUDIT Inspect the current project, FlutterFlow history, generated asset records, prior runtime evidence and available authenticated Preview network evidence. Do not check out or restore an older project revision. Determine for both assets: * Original: ChatGPT_Image_Jun_14,_2026_at_11_12_18_AM.png * Repaired: Chef_Proof_Command_Center.png Report: 1. FlutterFlow asset identifier 2. Registered source path or logical asset key 3. Generated runtime reference 4. Exact request destination category: * Packaged application asset * FlutterFlow Media Asset * Legacy FlutterFlow Storage * Firebase Storage * Signed remote URL * Other 5. HTTP status 6. Redirect chain 7. Response Content-Type 8. Response length 9. First-byte/file-signature classification 10. Whether the response is: * Valid PNG bytes * XML error document * HTML error document * JSON response * Empty body * Truncated image * Other 11. Whether the URL references the new safe filename or a stale legacy location 12. Whether the runtime binding uses the same asset record decoded by Media Assets 13. Whether URL encoding, authorization, cache metadata, service-worker state or asset-manifest state differs between Media Assets and authenticated Preview 14. Whether Preview returns an error payload with a misleading or missing image content type 15. Exact console error source and widget association For response comparison, record SHA-256 hashes where bytes are safely available. Do not expose: * Authentication tokens * Signed query parameters * Cookies * Session identifiers * Private Storage paths * User identifiers Redact sensitive URL portions in the final report. HISTORICAL REVISION INSPECTION Read-only inspect revision: vNs8uLxxXp2IW8lp8Z5Q Determine: * Whether Image_tgel0w5i referenced the correct new asset identifier * Whether generated code referenced Chef_Proof_Command_Center.png * Whether it instead resolved to the old asset record or legacy path * Whether the registered asset existed in the runtime manifest/package * Whether the failure occurred before or after Flutter’s image decoder received the payload Do not restore, apply, check out or rebind this revision. If evidence from the failed revision is unavailable, report the limitation. Do not recreate the failure by modifying the current page. COMPARATIVE CONTROL CHECK Use the working assets only as read-only controls: * 86_Proof_Logo_Background_Removed.png * Command_Center_Hero_Original.png Compare their successful runtime resolution with the failing Chef asset resolution: * Asset-record structure * Runtime reference type * Request destination * Status * Content type * File signature * Manifest presence * Cache behavior Do not modify either working asset. CLASSIFICATION Classify the blocker as one of: * Stale FlutterFlow asset binding or manifest reference * Authenticated Preview authorization failure * Legacy Storage resolution failure * Runtime asset packaging failure * Browser/service-worker cache mismatch * Registered asset-record corruption * FlutterFlow platform defect * Unable to determine Clearly separate confirmed facts from inference. SUPPORT EVIDENCE Determine whether the evidence is sufficient for a FlutterFlow Support escalation. If sufficient, prepare a concise support-ready incident summary containing: * Project name * Affected page and widget * Current FlutterFlow head * Failed historical binding revision * Asset filenames * Successful local and Media Assets decoding * Authenticated Preview failure * Sanitized request/response evidence * Reproduction steps * Expected result * Actual result * Confirmation that two other page assets render correctly * Confirmation that the error persists with a valid newly registered PNG * Confirmation that no backend or authentication mutation is involved Do not submit the support request. PROHIBITED ACTIONS Do not: * Modify any FlutterFlow object * Change an image binding * Upload or register another asset * Delete either asset * Rename an asset * Re-encode the artwork again * Try WebP, JPG, SVG or another PNG * Clear or change project data * Change authentication * Change routes * Change Storage * Change Supabase * Change the Command Center layout * Commit anything * Run the unfinished viewport, hard-refresh or navigation-return closure tests * Close V001C‑VR FINAL REPORT Report: * Preflight result * Starting and final FlutterFlow heads * Starting and final backend checkpoints * Workspace status * Original asset resolution path and response classification * Repaired asset resolution path and response classification * Working logo and hero control results * Media Assets versus authenticated Preview comparison * Historical binding inspection result * Exact confirmed failure layer * Whether the image decoder received PNG bytes or an error payload * Whether a stale legacy path remained involved * Whether cache or service-worker behavior is implicated * Sanitized reproduction steps * Recommended next action * Support-ready incident summary * Any evidence still missing * Confirmation that no project, asset, page, component, route, authentication, Supabase, Storage, Queue, Edge Function or application-data change occurred * Confirmation that no commit was created * Confirmation that V001C‑VR remains open Stop after reporting V001C‑VR‑R2‑P.

Visual documentation

Begin V001C‑VR‑R2‑P — FlutterFlow Runtime Asset Resolution Evidence Audit

PROJECT

Final Dashboard 86Proof MVP 3

REQUIRED FLUTTERFLOW HEAD

eS7pVCNnqPxNnOzbvg5Y

REQUIRED BACKEND CHECKPOINT

20260728193318_secure_upload_job_lifecycle_foundation

BACKGROUND

V001C‑VR‑R1 confirmed:

• The authoritative Chef Proof artwork is valid.
• Chef_Proof_Command_Center.png is a standards-compliant PNG.
• Dimensions: 1122×1402
• Color: 8-bit RGB, sRGB
• Encoding: non-interlaced
• Multiple local decoders succeeded.
• FlutterFlow Media Assets successfully registered and decoded the file.
• The Media Assets thumbnail decoded correctly.
• Decoded pixel hashes matched the authoritative artwork exactly.
• Filename punctuation was not the primary cause.
• Authenticated runtime Preview still reported:
  EncodingError: The source image cannot be decoded.

The original Chef image binding was restored after the repaired asset failed in runtime Preview.

Current project history:

• vNs8uLxxXp2IW8lp8Z5Q — repaired asset binding
• eS7pVCNnqPxNnOzbvg5Y — original binding restored

The repaired asset remains registered in Media Assets. Its deletion is not authorized.

PURPOSE

Perform a strictly read-only transport and resolution audit to determine what FlutterFlow authenticated runtime Preview actually requests and receives for the Chef Proof artwork.

Do not attempt another repair, conversion, upload, binding, filename, format, cache workaround or page modification.

PREFLIGHT

Confirm:

1. Local and server heads equal eS7pVCNnqPxNnOzbvg5Y.
2. Workspace is clean.
3. flutterflow ai test passes.
4. Backend checkpoint equals 20260728193318_secure_upload_job_lifecycle_foundation.
5. The V001C‑VR Command Center restoration remains present.
6. /commandCenterDashboard remains requireAuth: true.
7. The original Chef artwork binding is currently restored.
8. Chef_Proof_Command_Center.png remains registered in Media Assets.
9. No work occurred after V001C‑VR‑R1.
10. No Queue or Edge Function work has started.

Stop without changes if the checkpoints differ or the workspace is dirty.

READ-ONLY AUDIT

Inspect the current project, FlutterFlow history, generated asset records, prior runtime evidence and available authenticated Preview network evidence.

Do not check out or restore an older project revision.

Determine for both assets:

• Original:
  ChatGPT_Image_Jun_14,_2026_at_11_12_18_AM.png
• Repaired:
  Chef_Proof_Command_Center.png

Report:

1. FlutterFlow asset identifier

2. Registered source path or logical asset key

3. Generated runtime reference

4. Exact request destination category:

   • Packaged application asset
   • FlutterFlow Media Asset
   • Legacy FlutterFlow Storage
   • Firebase Storage
   • Signed remote URL
   • Other

5. HTTP status

6. Redirect chain

7. Response Content-Type

8. Response length

9. First-byte/file-signature classification

10. Whether the response is:

    • Valid PNG bytes
    • XML error document
    • HTML error document
    • JSON response
    • Empty body
    • Truncated image
    • Other

11. Whether the URL references the new safe filename or a stale legacy location

12. Whether the runtime binding uses the same asset record decoded by Media Assets

13. Whether URL encoding, authorization, cache metadata, service-worker state or asset-manifest state differs between Media Assets and authenticated Preview

14. Whether Preview returns an error payload with a misleading or missing image content type

15. Exact console error source and widget association

For response comparison, record SHA-256 hashes where bytes are safely available.

Do not expose:

• Authentication tokens
• Signed query parameters
• Cookies
• Session identifiers
• Private Storage paths
• User identifiers

Redact sensitive URL portions in the final report.

HISTORICAL REVISION INSPECTION

Read-only inspect revision:

vNs8uLxxXp2IW8lp8Z5Q

Determine:

• Whether Image_tgel0w5i referenced the correct new asset identifier
• Whether generated code referenced Chef_Proof_Command_Center.png
• Whether it instead resolved to the old asset record or legacy path
• Whether the registered asset existed in the runtime manifest/package
• Whether the failure occurred before or after Flutter’s image decoder received the payload

Do not restore, apply, check out or rebind this revision.

If evidence from the failed revision is unavailable, report the limitation. Do not recreate the failure by modifying the current page.

COMPARATIVE CONTROL CHECK

Use the working assets only as read-only controls:

• 86_Proof_Logo_Background_Removed.png
• Command_Center_Hero_Original.png

Compare their successful runtime resolution with the failing Chef asset resolution:

• Asset-record structure
• Runtime reference type
• Request destination
• Status
• Content type
• File signature
• Manifest presence
• Cache behavior

Do not modify either working asset.

CLASSIFICATION

Classify the blocker as one of:

• Stale FlutterFlow asset binding or manifest reference
• Authenticated Preview authorization failure
• Legacy Storage resolution failure
• Runtime asset packaging failure
• Browser/service-worker cache mismatch
• Registered asset-record corruption
• FlutterFlow platform defect
• Unable to determine

Clearly separate confirmed facts from inference.

SUPPORT EVIDENCE

Determine whether the evidence is sufficient for a FlutterFlow Support escalation.

If sufficient, prepare a concise support-ready incident summary containing:

• Project name
• Affected page and widget
• Current FlutterFlow head
• Failed historical binding revision
• Asset filenames
• Successful local and Media Assets decoding
• Authenticated Preview failure
• Sanitized request/response evidence
• Reproduction steps
• Expected result
• Actual result
• Confirmation that two other page assets render correctly
• Confirmation that the error persists with a valid newly registered PNG
• Confirmation that no backend or authentication mutation is involved

Do not submit the support request.

PROHIBITED ACTIONS

Do not:

• Modify any FlutterFlow object
• Change an image binding
• Upload or register another asset
• Delete either asset
• Rename an asset
• Re-encode the artwork again
• Try WebP, JPG, SVG or another PNG
• Clear or change project data
• Change authentication
• Change routes
• Change Storage
• Change Supabase
• Change the Command Center layout
• Commit anything
• Run the unfinished viewport, hard-refresh or navigation-return closure tests
• Close V001C‑VR

FINAL REPORT

Report:

• Preflight result
• Starting and final FlutterFlow heads
• Starting and final backend checkpoints
• Workspace status
• Original asset resolution path and response classification
• Repaired asset resolution path and response classification
• Working logo and hero control results
• Media Assets versus authenticated Preview comparison
• Historical binding inspection result
• Exact confirmed failure layer
• Whether the image decoder received PNG bytes or an error payload
• Whether a stale legacy path remained involved
• Whether cache or service-worker behavior is implicated
• Sanitized reproduction steps
• Recommended next action
• Support-ready incident summary
• Any evidence still missing
• Confirmation that no project, asset, page, component, route, authentication, Supabase, Storage, Queue, Edge Function or application-data change occurred
• Confirmation that no commit was created
• Confirmation that V001C‑VR remains open

Stop after reporting V001C‑VR‑R2‑P.

Environment

- FlutterFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

No response

[Alezanello]

Hello!!

Can you give us a direct way to reproduce this issue?