New answers tagged


Unfortunately, there's not much you can do. You'd have to be in the same namespace in order to access the values, and you can't have a 1GP and 2GP with the same namespace installed in the same org. The only real path forward is to migrate your 1GP to a 2GP, which, as I understand it, won't be available until at least 2022. A potential workaround for now ...


Yes, this will work (provided you link your namespace to both Dev Hubs), and you won't have any ancestry issues. But you also don't need to do this at all. You can just change the name of your package in the experimental fork if you want to have an independent package with the same namespace. Your Dev Hub can own both just fine, and they won't have any ...


You cannot migrate a package directly from one org to another; you have to create a new one. Similarly, you cannot specify an ancestor package version or a package Id from a different Dev Hub org. In other words, by abandoning your old Dev Hub org, you are also going to have to abandon your package and all versions created so far. You will have to create a ...


After many hours of trial and error, I realized the issue was caused by how I logged into the organisation. Using sfdx force:org:open does not provide the correct context for REST API usage. Instead you need to generate a password for the user account using sfdx force:user:password:generate and login through the lightning login portal.

Top 50 recent answers are included