It seems because the output of building a static framework goes to Carthage/Build/iOS/Static/XYZ.framework (an additional Static directory), the archive script doesn't find it, outputting:
Could not find any copies of EngageSDK.framework. Make sure you're in the project's root and that the frameworks have already been built using 'carthage build --no-skip-current'.
And that's happening when both invoking carthage build --archive or carthage build --no-skip-current && carthage archive
Also wanted to confirm, is it expected that static frameworks won't have DSYM and bcsymbolmap files generated?
static frameworks won't have DSYM and bcsymbolmap files generated
that is expected.
Do you want to give this a shot @sirghi ?
I'll try.
On a relatively related note, would you be able to take a look at #2618 @blender ? If you have time
Is there any workaround for archiving static frameworks ? Manually ?
@vitorhugomagalhaes well if you run carthage build --no-skip-current, the framework will be generated correctly. It's just the zip file creation that will fail.
@sirghi Yes. Thanks.
Have experienced this issue as well. The only problem is that the static sub-directory isn't considered for finding the framework. Otherwise it works fine, and you could zip the Carthage directory manually. Seems like a quick fix
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is not stale. carthage build --archive should work for static frameworks.
Is there an update on this? It looks like it's still busted.
@jbfitb I've submitted a PR for it. ^
Most helpful comment
This issue is not stale.
carthage build --archiveshould work for static frameworks.