Skip to content
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

App build fails due to missing dependencies #1755

Closed
hansemannn opened this issue Jun 8, 2023 · 7 comments · Fixed by #1756 or #1833
Closed

App build fails due to missing dependencies #1755

hansemannn opened this issue Jun 8, 2023 · 7 comments · Fixed by #1756 or #1833
Assignees

Comments

@hansemannn
Copy link

Which version of the Ably SDK are you using?

1.2.20

On which platform does the issue happen?

iOS 16.4

Are you using Carthage?

Yes, 0.38.0

Are you using Cocoapods?

Yes, 1.11.3

Which version of Xcode are you using?

14.3

What did you do?

The build fails when including the framework - tried with the attached framework via Github releases, Carthage and Cocoapods.
Screenshot 2023-06-08 at 10 39 57

'ARTTypes.h' file not found

What did you expect to happen?

The build should succeed.

What happened instead?

The build should fails with the above error message.

@sync-by-unito
Copy link

sync-by-unito bot commented Jun 8, 2023

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3628

@hansemannn
Copy link
Author

Workaround for now: Fix the invalid reference of headers inside private headers by using a module-based import:

- #import "ARTTypes.h"
+ #import <Ably/ARTTypes.h>

@maratal
Copy link
Collaborator

maratal commented Jun 8, 2023

Hey @hansemannn Couldn't you test the branch from this PR #1756 whether it works for you. Thanks.

@hansemannn
Copy link
Author

@maratal Looks promising! This should work, thank you!

@lawrence-forooghian
Copy link
Collaborator

Re-opening this one to see if we can reproduce it ourselves, and so we can update our CI to catch issues like this in the future.

@lawrence-forooghian
Copy link
Collaborator

Hi @hansemannn, we'd like to reproduce this issue before we attempt a fix for it. Might you be able to share with us an Xcode project which exhibits the issue that you've described?

@hansemannn
Copy link
Author

As the workaround to manually fix the import worked, so project is completed for now. A simple Swift-based project that uses manual framework inclusion (no SPM or Cocoapods) should reproduce it. If I get some additional time, I'll try to provide the project as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants