cloudinary / cloudinary/cloudinary-react-native
Expo dependency error, "Cannot find native module 'ExpoCrypto'", in Non-Expo React Native Projects
- 主要語言
- TypeScript
- 星號
- 28
- 分支
- 21
- PR 合併指標
- 30 天內沒有已合併 PR
描述
I encountered an issue while integrating the cloudinary-react-native package version 0.2.0 into my bare React Native project. The problem arises due to the package's dependency on ExpoCrypto and other Expo modules, which are not available in a non-Expo (bare) React Native environment.
### Steps to Reproduce
1. Create a new bare React Native project using npx react-native init MyProject.
2. Install the cloudinary-react-native package using npm install cloudinary-react-native.
3. Attempt to use the package according to the provided documentation.
4. Encounter an error related to the missing ExpoCrypto module when running the app.
### Expected Behavior
I expected that the cloudinary-react-native package could be used in a bare React Native project without dependencies on Expo-specific modules, or that there would be clear documentation on how to handle such dependencies in a non-Expo environment.
```
import {Cloudinary} from '@cloudinary/url-gen';
import {upload} from 'cloudinary-react-native';
async function uploadImageToCloudinarySDK(payload: any) {
const {folder, upload_preset, uri} = payload;
const cld = new Cloudinary({
cloud: {cloudName: Config.CLOUDINARY_CLOUD_NAME },
url: {secure: true},
});
const options = {folder, upload_preset, unsigned: true};
await upload(cld, {
file: uri,
options,
callback: (error: any, response: any) => {
if (error) {
console.error('Upload Error:', error);
} else {
console.log('Upload Successful:', response);
}
},
}).catch((error: any) => console.log('ERROR CLD UPLOAD', error?.message));
}
```
### Actual Behavior
The application throws an error indicating that the ExpoCrypto native module cannot be found. This suggests that the package relies on Expo modules, which are not present in bare React Native environments. The exact error message is:
`Cannot find native module 'ExpoCrypto', js engine: hermes`
### Environment
- React Native version: 0.73.2
- Cloudinary React Native SDK version: 0.2.0
- Operating System: iOS
- Device details: iPhone 15 Pro Max
### Additional Context
I am not using Expo in my project and prefer to keep it as a bare React Native application. I noticed that the package-lock.json file lists several Expo-related dependencies, which might be causing this issue.
Given the package's potential utility for React Native developers looking to integrate Cloudinary, finding a solution to make it compatible with both Expo and non-Expo environments would be greatly beneficial.
### Potential Solutions or Workarounds
I am seeking guidance on how to resolve this issue. Possible solutions could include:
- Instructions on how to remove or bypass the Expo dependencies in a non-Expo environment.
- Updates to the package to support bare React Native projects without requiring Expo modules.
- Any other recommended approaches for using cloudinary-react-native in non-Expo React Native projects.
Thank you for looking into this issue. I appreciate any feedback or solutions you can provide.
貢獻指南
研究方向
使用 React Native 0.73.2、cloudinary-react-native 0.2.0 以及 issue 中描述的 bare project 設定重現此故障。首先檢查 package-lock.json 和該套件與 Expo 相關的相依性;當 SDK 能在 bare React Native 應用程式中運作,或記錄所需的 workaround 和支援的設定時,即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- react-native, typescript
- 領域
- mobile
- Issue 類型
- 缺陷
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100