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

A compilation error using Xcode 16 #35

Closed
MaximLitvinyuk opened this issue Sep 16, 2024 · 11 comments
Closed

A compilation error using Xcode 16 #35

MaximLitvinyuk opened this issue Sep 16, 2024 · 11 comments

Comments

@MaximLitvinyuk
Copy link

Projects using Xcode 16 and the latest ios-webui-sdk release (3.4.2) will not compile because of the next error:

/Users/max/Library/Developer/Xcode/DerivedData/ios-webui-sdk-example-apxgnkmypgwhrjemxlegjwpayugr/SourcePackages/checkouts/ios-webui-sdk/QueueItLib/QueueService_NSURLConnectionRequest.h:19:1 'QueueService_NSURLConnectionRequestDelegate' has different definitions in different modules; first difference is definition in module 'QueueITLibrary' found method 'requestDidComplete:' with 1st parameter of type 'QueueService_NSURLConnectionRequest *__strong'

The example project where it can be reproduced can be found here:
https://github.com/MaximLitvinyuk/ios-webui-sdk-example-xcode-16-error

NOTE: in order to reproduce it, you should run the project using Xcode 16

@3520kramer
Copy link
Contributor

@MaximLitvinyuk Thanks for providing us with this information and including a project to reproduce in. Do you have a workaround or is this a complete blocker for you?

@sbo-nemlig
Copy link

I can see that @MaximLitvinyuk has also submitted a PR for the fix #36

@3520kramer
Copy link
Contributor

Yes thanks, we are aware of the PR. What i would like to know is if @MaximLitvinyuk can use the workaround without us releasing a new version or if it's a complete blocker? And i would like to know if this is the case for you @sbo-nemlig as well?

@sbo-nemlig
Copy link

Yes, this issue is preventing us from using Xcode 16 and iOS 18. I'm not sure if there's a workaround other than using @MaximLitvinyuk's fork, as the problem seems to be related to naming conventions within your SDK.

@3520kramer
Copy link
Contributor

Would you be able to use that until we have released a fix for this issue? ETA is beginning of next week

@sbo-nemlig
Copy link

Yes, we can also wait a week if that is the ETA

@3520kramer
Copy link
Contributor

That's great! Thank you for the patience

@MaximLitvinyuk
Copy link
Author

MaximLitvinyuk commented Sep 19, 2024 via email

@MaximLitvinyuk
Copy link
Author

MaximLitvinyuk commented Sep 25, 2024 via email

@3520kramer
Copy link
Contributor

We are expecting to be able to release a new version by end of today or tomorrow. Thanks for the patience

@3520kramer
Copy link
Contributor

We have released version 3.4.3 which should solve the issue. Please open a new issue if the error persists

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

No branches or pull requests

3 participants