trailheadapps/ebikes-lwc

Deploy Failed

ameryehia opened this issue · 6 comments

Summary

DEPLOY PROGRESS | ████████████████████████████████████████ | 99/99 Components
Hello,
The SFDX Push Failed to deploy after following all steps in the deployment steps
https://github.com/trailheadapps/ebikes-lwc/blob/main/README.md#installing-e-bikes-using-a-developer-edition-org-or-a-trailhead-playground
=== Component Failures [1]

Type Name Problem

───── ──────── ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Error E_Bikes1 We couldn't validate componentAttributes in E_Bikes1/themes/jepson.json for component f78b9665-bf73-45c3-b5e1-8bf378c0c8d4.
Error: attribute [navigationMenuEditorRefresh]: The navigation menu Default Navigation doesn’t exist.. Check your file and try again.

ERROR running force:source:deploy: Deploy failed.

Salesforce Org Type

Developer Edition Org

Steps To Reproduce

sfdx force:source:deploy -p force-app

Current Behavior

Error E_Bikes1 We couldn't validate componentAttributes in E_Bikes1/themes/jepson.json for component f78b9665-bf73-45c3-b5e1-8bf378c0c8d4.
Error: attribute [navigationMenuEditorRefresh]: The navigation menu Default Navigation doesn’t exist.. Check your file and try again.

Expected Behavior

deployment success

Relevant Log Output

Error E_Bikes1 We couldn't validate componentAttributes in E_Bikes1/themes/jepson.json for component f78b9665-bf73-45c3-b5e1-8bf378c0c8d4. 
Error: attribute [navigationMenuEditorRefresh]: The navigation menu Default Navigation doesn’t exist.. Check your file and try again.

Code of Conduct

  • I agree to follow this project's Code of Conduct
pozil commented

@ameryehia are you trying to deploy to a Winter '23 org?
We haven't migrated the metadata to API v56 yet so this could explain the issue.

Yes :) Thank you Pozil for taking the time to answer my issue, it's just relief that i'm not the cause of the error 👍 :D

i am getting similar error @pozil on mydevorg which is spring 23 release. Note sure if i missed note somewhere but I can try with release where it works on scratch org?
Error :
DEPLOY PROGRESS | ████████████████████████████████████████ | 98/98 Components

=== Component Failures [2]

Type Name Problem
───── ────────────────── ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Error E_Bikes1 We couldn't validate componentAttributes in E_Bikes1/themes/jepson.json for component f78b9665-bf73-45c3-b5e1-8bf378c0c8d4. Error: attribute [navigationMenuEditorRefresh]: The navigation menu Default_Navigation doesn’t exist.. Check your file and try again.
Error Default_Navigation This site already includes a menu called Default Navigation. Enter a unique name.

Error (1): Deploy failed.

pozil commented

Hi @myautogit it's this time of the year again where some orgs are starting to get the Summer '23 pre-release.
I've already identified some breaking changes in Experience Cloud metadata in the upcoming release so I'm going to work on fixing those in a prerelease/summer23 branch.

In the meantime the project should work as expected on Spring '23 (our CI guarantees this).

How to handle deployment error
Uploading IMG20230913145205.jpg…

Could please help me