Error: Cannot find native module 'ExponentAV'

[josephng2003]

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.

Requires 'ExponentAV' while I have expo-av installed

Issue Type (Can be multiple)

[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[X] Behaviour - Requires 'ExponentAV' while I have expo-av installed
[ ] Documentation - Inconsistency between the docs and behaviour
[ ] Other (Specify)

Code snippet

Error screenshots or Stack Trace (if applicable)

Is the issue reproducible only on a specific device?

[X] No
[ ] Yes (specify device model + iOS/Android version)

Versions and Libraries (fill in the version numbers)

React Native Cloudinary SDK version - 1.0.0
Android Studio - 2024.1.2
TargetAndroid - 14

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

[kiran1201w]

I have the same issue here cannot play audio files

[farmhutsoftwareteam]

Avoiding incompatible updates
The main issue that can arise when publishing updates is that the update could rely on native code that the build it's running on does not support. For instance, imagine we made a build with a runtime version of "1.0.0". Then, we submitted that build to the app stores and released it to the public.

Later on, imagine that we developed an update that relied on a newly installed native library, like the expo-camera library, and we did not update the "runtimeVersion" property, so that it is still "1.0.0". If we published an update, the builds with the "runtimeVersion" of "1.0.0" would think the incoming update with the same runtime version was compatible and it would attempt to load the update. Since the update would make calls to code that does not exist inside the build, expo-updates may detect an error and attempt to roll back to the previously working update (learn more about error recovery behavior).

The following are some strategies to avoid deploying updates that are incompatible with a build's native code.

Use a runtime version policy that automatically updates the runtime version when native code is updated
The "appVersion" policy will increment the runtime version whenever the app version is incremented, but if you forget to bump the app version when changing the native runtime, then you'll have a runtime version mismatch. If you want to make incompatible updates extremely unlikely, at the cost of making it necessary to create builds more often, then you can use the "fingerprint" policy. This will increment the runtime version whenever anything that may impact the native runtime changes (learn more about fingerprinting).

[dannyv-cloudinary]

Hey. We actually made a small change yesterday which you can see here: adef2a1
We don't bundle it by default, but you should be able to run npm install expo-av to get the package