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 when FlowScreenComponentsBasePack to v 3.3.5.0 #1590

Open
alfonzajackson opened this issue Sep 27, 2024 · 4 comments
Open

Error when FlowScreenComponentsBasePack to v 3.3.5.0 #1590

alfonzajackson opened this issue Sep 27, 2024 · 4 comments

Comments

@alfonzajackson
Copy link

Current version is 3.3.4 in our environments. I'm getting the following error in all environments when attempting to upgrade to the latest version:

 
Your request to install package "FlowScreenComponentsBasePack 3.3.5.0" was unsuccessful. None of the data or setup information in your salesforce.com organization was affected.

If your install continues to fail, contact Salesforce CRM Support through your normal channels and provide the following information.

Organization: Ochsner Health (00D23000000G9n4)
User: Alfonza Jackson (0052H00000C5tZ9)
Package: FlowScreenComponentsBasePack (04t5G000004fz8z)

Problem:

  1. LightningComponentBundle(fsc_pickObjectAndField3) lwc/fsc_pickObjectAndField3/fsc_pickObjectAndField3.js-meta.xml: You can’t remove the following public properties: testproperty, because the component is part of a managed package.
    fsc_pickObjectAndField3: lwc/fsc_pickObjectAndField3/fsc_pickObjectAndField3.js-meta.xml: You can’t remove the following public properties: testproperty, because the component is part of a managed package.
@alfonzajackson
Copy link
Author

Other affected ORGS:
00DDO0000008aRb
00D1U000000wLD3

@jessepink
Copy link

I'm also getting this error message when attempting to upgrade.
Installed: 3.2.2.0 (3.2.2) New Version: 3.3.5.0 (3.3.5)

@jessepink
Copy link

I was able to just upgrade from 3.2.2.0 to 3.3.4.0 without issue, then I tried to go from 3.3.4 to 3.3.5 and got the same error as those above.

@ericrsmith35
Copy link
Collaborator

ericrsmith35 commented Oct 9, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants