-
Notifications
You must be signed in to change notification settings - Fork 91
Build Error with SDWebImage Version 5.18.0+ #84
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
Comments
5.18.0 -> 5.18.1 Does not add new header files or source files...The tag diff is here: https://github.com/SDWebImage/SDWebImage/compare/5.18.0..5.18.1 The only change is |
How Tuist works on Swift Package Manager framework ? I have no knowledge about that. |
Guess this change cause the issue
But I don't know how the correct way to solve this. SDWebImage itself does not use any non-modular headers ? Always using |
Any update here? |
I didn't see any error in SDWebImage's standard unit test on integration. If you face issue, provide the reproduce demo, so that we can try to investigate.🤔️ Not the sample code, I mean a reproducible demo, like a zip archive or git repo@rishabh876 Any demo ? |
Here is my test Demo, using Swift PMSDWebImageSwiftPMObjc.zip I didn't find anything integration issue. Screenshot![]() ![]() Xcode VersionXcode 14.3.1 |
Ok it looks like I am also using 5.18.5 that should have the fix but still the images are getting upside down while encoding.
|
That fix is for JPEG only, not the WebP encoding. Maybe new bugs |
Can you create a new issue instead ? So I can create PR directly point to that. This PR seems out of date and non-related, I'll close now |
@rishabh876 Create a new issue with your demo ? I can not reproduce with the description you say. For example
|
The build issue no long exists and close |
Uh oh!
There was an error while loading. Please reload this page.
Currently, I'm managing project dependencies using Tuist.
Versions:
macOS
13.5.2
Xcode
14.3.1
SDWebImage
5.18.2
SDWebImageWebPCoder
0.13.0
Build Error Details:
Upon direct testing, I found that the error mentioned above starts occurring from version 5.18.1 of SDWebImage.
By locking the SDWebImage version to 5.18.0, the error no longer arises.
I'm not sure why this error is occurring due to the version difference. Please help.
The text was updated successfully, but these errors were encountered: