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

Bad version of the SoLoader SDK used in Cloudinary Download SDK #169

Open
ivanovmeya opened this issue Aug 29, 2024 · 3 comments
Open

Bad version of the SoLoader SDK used in Cloudinary Download SDK #169

ivanovmeya opened this issue Aug 29, 2024 · 3 comments

Comments

@ivanovmeya
Copy link

Bug report for Cloudinary Android SDK

com.cloudinary:cloudinary-android-download:2.8.0 depends on facebook fresco 2.6.0 (com.facebook.fresco:fresco:2.6.0), which uses bad version of SoLoader. 0.10.1

Describe the bug in a sentence or two.

When I try to upload release build to Google Play console, while automatic checks it rejects the build with error:

Bad version of the SoLoader SDK
Your app uses a version of the SoLoader SDK that can cause crashes on 64 bit-only devices. To resolve this, update the SoLoader SDK to version 0.10.4 or higher.

Please update Fresco dependency, otherwise people using your SDK can't upload releases to GP

image
@dannyv-cloudinary
Copy link

Hey @ivanovmeya.
Thanks for flagging this. This isn't a direct dependency of ours, but rather, a dependency of one of our dependencies.
That being said, we have identified where this issue is coming from and have ticketed this up internally (ref SNI-8215) to get resolved in the next few sprints.

Once we have an update to provide, I'll let you know here.

Thanks!

@TomBell-Trove
Copy link

As a workaround you can force gradle to use a safe version of soloader.

    implementation(libs.cloudinary)
    constraints {
        implementation("com.facebook.soloader:soloader:0.10.4") {
            because("previous versions crash on some 64bit devices")
        }
    }

@momoip
Copy link

momoip commented Sep 25, 2024

Hey @ivanovmeya,
The issue has been resolved. Please let us know if it works for you.
Thanks,

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

4 participants