Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error deploying to SDO #672

Closed
1 task done
eltoroit opened this issue Apr 1, 2024 · 2 comments
Closed
1 task done

Error deploying to SDO #672

eltoroit opened this issue Apr 1, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@eltoroit
Copy link

eltoroit commented Apr 1, 2024

Summary

Step 6 sf project deploy start -d force-app is not working. I get this error:

You seem to be missing the property favIconAssetRef in E-Bikes/config/mainAppPage.json with component ID: 591ae89d-97d7-4f5d-b93f-ce618e5d48f1

Salesforce Org Type

Production Org

Steps To Reproduce

I am installing this project in an SDO following the steps in the README.md file but the deployment (sf project deploy start -d force-app) is failing.

Current Behavior

I get this error:

You seem to be missing the property favIconAssetRef in E-Bikes/config/mainAppPage.json with component ID: 591ae89d-97d7-4f5d-b93f-ce618e5d48f1

Expected Behavior

No errors, and deployment succesful

Relevant Log Output

==========================================================================================================================================================================================================
| Type    Name                                 Problem                                                                                                                                         Line:Column 
| ─────── ──────────────────────────────────── ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ─────────── 
| Error   Default_E-Bikes                      Audience needs at least one criteria.                                                                                                                       
| Error   Default_Navigation                   In field: Network - no Network named E-Bikes found                                                                                                          
| Error   E-Bikes                              PicassoSite E_Bikes1 not found                                                                                                                              
| Error   E_Bikes                              In field: Name - no Network named E-Bikes found                                                                                                             
| Error   E_Bikes1                             You seem to be missing the property brandingSetType in E-Bikes/brandingSets/jepson.json with component ID: 26ab9e87-e30e-419f-b5b6-e054218fcee7             
| Error   SFDC_Default_Navigation_EUU002dBikes In field: Network - no Network named E-Bikes found                                                                                                          
| Error   cbE_Bikes                            Network not found for the CustomBrand : cbE_Bikes                                                                                                           
| Error   ebikes                               Permission Read Account depends on permission(s): Read Contact                                                                                              
| Warning ebikeslogo                           This record isn't in the target org: E-Bikes.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@eltoroit eltoroit added the bug Something isn't working label Apr 1, 2024
Copy link

github-actions bot commented Apr 1, 2024

Thank you for posting this issue. 🙇🏼‍♂️
We will come back to you shortly.

@pozil
Copy link
Contributor

pozil commented Apr 2, 2024

Hi Andres, sorry but we don't support SDO for our sample apps because there are way too many metadata and custom settings in these orgs that can conflict with our setup. As per our doc we recommend using clean orgs (scratch org, DE org or a playground).

You're welcome to try the deployment but it's going to take several iterations. In your case I would make sure that Experience Cloud is enabled and look into access rights because this error sounds like the root cause:

Permission Read Account depends on permission(s): Read Contact

@pozil pozil closed this as completed Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants