-
Notifications
You must be signed in to change notification settings - Fork 38
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
sfdx texei:package:dependencies:install command retrieving wrong package version Id #53
Comments
Yes please, if you have a reproducible example this would help. |
my unlocked package is called (this is what is in the sfdx-project.JSON under the dependencies key
Info retrieved when running sfdx force:package:version:list -p PACKAGEID (showing that is it the latest package and is released)
After running sfdx texei:package:dependencies:install -r
So it pulls down a different Package Version ID, which is weird, then received this error
|
Ok thanks, we'll have a look. |
Much appreciated Fabien |
@Bgallahue can you tell me what is the version number of the Package Version Id retrieved by the Texeï plugin ? |
Also, can you list what's under your |
I have received this error a couple times using the sfdx texei:package:dependencies:install command
AppExchange Package is Deprecated, Details: The AppExchange package has been deprecated and can no longer be installed. Please try installing a newer version, or contact the package owner directly to resolve.
This occured not on a Appexchange package but rather just on one of my normal Unlocked package. I am not positive where it is pulling the package version Id from as in the latest instance in which I received the error, no package version in the history of that specific unlocked package had the same PackageVersionId as what the command tried to use (ie. it didnt use an old one)
I was able to manually install the error generating package using sfdx force:package:install. It was about the 5th package down in the dependency tree. Let me know if you need any additional info or anything was unclear
The text was updated successfully, but these errors were encountered: