Didn't fix the resolved file, same error. I just tried removing it and re-adding it to the Xcode project. Xcode re-creates it, but it's always missing that one package, despite it being in the project list of dependencies. I just tried deleting the resolved file again. The one missing package is not in the Package.resolved file. There are no errors in the resolution log. So I reset the cache, and that seemed like it was working, but when it was all done, there was still one missing package. I told Xcode 13b1 to Resolve Package Versions, but that didn't seem to do anything. I discarded it, and ran into the problem. I had a merge conflict with Package.resolved (not sure why it keeps changing). I've been building just fine with a dozen SPM dependencies, and am now running into this. Note: Using build description from memoryĮrror: Missing package product 'Deeplinks' (in target '' from project '')Įrror: Missing package product 'LocationProvider' (in target '' from project '')Įrror: Missing package product 'Countr圜odes' (in target '' from project '')Įrror: Missing package product 'ReachabilityInternetProvider' (in target '' from project '')Įrror: Missing package product 'LanguageCodes' (in target '' from project '')Įrror: Missing package product 'BaggageDistributor' (in target '' from project '') Package resolution log: Showing All MessagesĪctivity Log Complete, 10:31 0.6 seconds Is there anything we can do to help get this fixed? What works for me is closing the workspace before switching branches. Our team is also experiencing this - we use both Cocoapods (for now) and SPM and our local packages do this every time we switch branches. Package Resolution log: Showing All MessagesĪctivity Log Complete 6/30/20, 11:26 AM 7.5 secondsīuild target of project with configuration DebugĮrror: Missing package product '' (in target '' from project '')īuild failed 6/30/20, 11:19 AM 1.2 seconds The error above is specifically for local packages only. Looks like it only applies to remote swift packages. You can easily support by checking out this sponsor.The Package resolution log shows no errors. Selecting a Swift toolchain in Xcode will affect the Xcode IDE only. Xcode uses the selected toolchain for building Swift code, debugging, and even code completion and syntax coloring. Click indicator icon will open up Components preferences, where you can change back to the default one. When an alternative toolchain is chosen, you will see a new toolchain indicator in Xcode's toolbar. You will see it once you installed the toolchain. The Toolchains tab only shows up if you have more than one toolchain. You will see all available toolchains, select our newly installed one. Open Xcode’s Preferences ( ⌘ - command + ,), navigate to Components tab, then select Toolchains. So, don't worry if you don't see this menu. This menu only shows up if you have more than one toolchain. You can find the Toolchains menu under Xcode menu, where you can easily switch between installed Swift toolchains. Choose the new toolchain in XcodeĪfter installing a new toolchain, we need to tell Xcode to use this new toolchain. Sponsor and reach thousands of iOS developers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |