A problem occurred evaluating project ':expo-application'. After install SDK in Expo

[Betoml5]

Bug report for Cloudinary React Native SDK

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

Describe the bug in a sentence or two.

I was using the SDK with Expo go and was working well after i tried to do it with Development build and when i tried to run
npx expo run:android the build crashes. At the first time i didn't know what was it but i created a empty project and worked well so i uninstalled some libraries and after some changes i realized the SDK was the problem. I dont know why is just on Development build

Issue Type (Can be multiple)

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

Steps to reproduce

… if applicable

Error screenshots or Stack Trace (if applicable)

Build/Dependency management

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

Is the issue reproducible only on a specific device?

[ ] No
[ ✅] Yes (specify device model + iOS/Android version)
I haven't tried on iOS but in android is happening

Versions and Libraries (fill in the version numbers)

React Native Cloudinary SDK version - 1.0.0
OSX (on the dev environment) - 0.0.0
XCode/Android Studio - 0.0.0
Swift/Java/Kotlin - 0.0.0
Target iOS/Android - 0.0.0

Repository
If possible, please provide a link to a reproducible repository that showcases the problem

[wissam-khalili]

Hi @Betoml5 ,

From the error message, it seems that there is a problem with the expo-application package, specifically related to Gradle configuration. The error message indicates that the build is failing due to an unknown property classifier for the task :expo-application:androidSourcesJar.

I would suggest updating dependencies and try clearing the gradle cache and rebuilding the project.

Thanks,
Wissam

[vedantb2]

@wissam-khalili I have the same error, tried rebuilding the project but the error still appears.

[BastienPailloux]

Hi,
It's a dependency issue.
Since Expo SDK51 all expo-packages had made a major update. Cloudinary-React-native need to be updated.

I've created a PR but I'm waiting for a review.

Until to be updated, you can do it by yourself:

You can fork Cloudinary-React-Native and update all dependencies of expo-package to the latest version. And after you can import your own forked repository into your project.

Hope it will help until the update of Cloudinary

[Betoml5]

@wissam-khalili I have the same error, tried rebuilding the project but the error still appears.

Hi, what i did was use the Upload API

https://api.cloudinary.com/v1_1//<resource_type>/upload

With this i was able to upload my assets in my case images.

https://cloudinary.com/documentation/upload_images#landingpage

[wissam-khalili]

Hi @Betoml5 ,

Thank you for the update.
I’ll investigate the root cause of this issue internally and get back to you.

Best Regards,
Wissam

[BastienPailloux]

Hi @wissam-khalili,

Do you have any news?
For me it's just a dependency issue, I've made a PR and it's workng perfectly (while I get the same error as @Betoml5 on expo-asset, expo-av and expo-crypto).

On Expo SDK51 they access differently to expo-packages and therefore all of them where updated. But on Cloudinary you still request the old version of the expo-packages.
On older version of Expo cloudinary is working fine, but in my case I cannot come back on older Expo versions.

Best

[wissam-khalili]

Hi @BastienPailloux,

Thank you for your input.
I will share this information with the developer to review this issue.
I will keep you posted.

Thanks,
Wissam

[wissam-khalili]

Hi @BastienPailloux ,

I can see that the code was merged:
#28

Thanks,
Wissam

[rnarang-goauto]

Hi @wissam-khalili
is there any plan to release the new sdk version with this fix ?

Thanks,
Rahul

[tommyg-cld]

@rnarang-goauto it should be released in the next few weeks.

[tommyg-cld]

the fix for this was released yesterday so please update to the latest version and let us know if you still see the same issue.

[BastienPailloux]

It works on my project after updating
Thanks @tommyg-cld