Geek Answers Handbook

There is no such module only when archiving

I am using xcode 7.3.1 at the moment. I have a workspace configured using an iOS application app and two infrastructure projects.

  • MyiOSApp (import 2 and 3)
  • AppSharedFramework (import 3)
  • CompanySharedFramework (This we will one day divide into our own business)

I can build each of these projects perfectly when working on a simulator, I can also build everything for Profiling (which uses the release build). But as soon as I try to archive 1 or 2, the assembly will fail with "There is no such module" CompanySharedFramework "

I tried to get this for quite some time, which may cause this problem during the archive, but not during the run / profile build.

Any thoughts?

+7
source share
4 answers

In my main project, a long time ago, I created a new “configuration scheme” called “AppStore” that was duplicated from the default “Release” Xcode configuration. I added the whole Xcode project (framework project) to my project. I was able to @import MyFramework; when "Launch" because both projects had "Debug" as the scheme for the "Launch" application. When I went to the archive, my main project was configured to use the "AppStore" configuration (as opposed to the "Release" default), and my subproject did not have the "AppStore" configuration. As soon as I added the “AppStore” to the “Release” -based subproject, when I went to the archive, it worked perfectly, was completely built, because both projects now had an AppStore scheme, and the main project is the one that says it uses this configuration when archiving, so when I just created it in a sub-project, everything started working as you expected.

+3
source

If you use the pod file in your project, please run the pod install command even if you have already run the command. Good luck

0
source

@ John Erk and @ Victor Poroshenko inspired me.

Only one rule, if the main project has a configuration named "AppStore", the subprojects in the same workspace that is used by your main project also require a configuration called "AppStore".

Two situations in my case:

  1. For the subproject that you imported into the workspace manually, add the "AppStore" for it manually.
  2. For pod files, just run pod install , it will generate the missing Pods-PROJECT_NAME.appstore.xcconfig for you.
0
source

Try deleting the Pods folder, workspace, and PodFile. Lock and reinstall Pod.

0
source

More articles:


All Articles