cloudinary / cloudinary/cloudinary-react-native
A problem occurred evaluating project ':expo-application'. After install SDK in Expo
- Langage dominant
- TypeScript
- Étoiles
- 28
- Forks
- 21
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
## 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
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par reproduire l’échec du build de développement Android avec `npx expo run:android` en utilisant la version 1.0.0 du Cloudinary React Native SDK, puis comparez-le au projet Expo vide qui fonctionnerait d’après le rapport. Examinez la capture d’écran de l’erreur jointe ainsi que la configuration Expo/React Native du projet ; le travail sera considéré comme terminé lorsqu’une cause reproductible aura été identifiée et que l’échec du build spécifique au SDK aura été documenté ou corrigé.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- react-native, typescript
- Domaine
- build-system, mobile
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100