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

404 responses are still written to the cache #278

Öffnen Sie
antoniostrijdom opened this issue Nov 10, 2020 · 2 comments
Öffnen Sie

404 responses are still written to the cache #278

antoniostrijdom opened this issue Nov 10, 2020 · 2 comments
Assignees
Labels

Kommentare

@antoniostrijdom
Copy link

Bug report for Cloudinary iOS SDK

Before proceeding, please update to latest version and test if the issue persists

Describe the bug in a sentence or two.

When the cloudinary URL request fails with a 404, the downloadImageAndCacheIt function still attempts to write a 0 byte file to the cache.

Issue Type (Can be multiple)

[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[x] Behaviour - Functions aren’t working as expected (Such as generate URL)
[ ] Documentation - Inconsistency between the docs and behaviour
[ ] Other (Specify)

Steps to reproduce

Simply call CLDDownloader.fetchImage(_:_:completionHandler:) with an invalid URL.

Error screenshots or Stack Trace (if applicable)

The following error is raised:

        {
        "error_code" = "-7001";
        "error_domain" = "com.cloudinary.error";
        "user_info" =         {
            NSLocalizedFailureReason = "Failed creating an image from the received data.";
        };

There was no received data.
image

Build/Dependency management

[x] Cocoa-Pods
[ ] Carthage
[ ] Manual import
[ ] Other (Specify)

Is the issue reproducible only on a specific device?

[x] No
[ ] Yes (specify model + iOS version)

Versions and Libraries (fill in the version numbers)

iOS Cloudinary SDK version - 2.9.0
OSX (on the dev environment) - 10.15.6 (19G73)
XCode - 12.1 (12A7403)
Swift - 5
Target iOS - 14.1

@asisayag2 asisayag2 assigned asisayag2 and nitzanj and unassigned asisayag2 Nov 11, 2020
@michalkcloudinay
Copy link
Contributor

Hi @antoniostrijdom, we are further investigating this issue and will update you with any new information. Thanks

@AlexPinhasov
Copy link
Contributor

Hello @antoniostrijdom, is this still an issue?
We have implemented a new caching mechanism on April 2021, can you please try and update to the latest version and check back with me?

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

No branches or pull requests

5 participants