You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I face this issue with expo prebuild in android I have add BLUETOOTH_CONNECT to my AndroidManifest.xml also request permission but still not work does this repo support only bare react native ?
To Reproduce
yarn add react-native-rtmp-publisher
set up RTMPPublisher component
crashed
Describe the bug
I face this issue with expo prebuild in android I have add BLUETOOTH_CONNECT to my AndroidManifest.xml also request permission but still not work does this repo support only bare react native ?
To Reproduce
yarn add react-native-rtmp-publisher
set up RTMPPublisher component
crashed
Expected behavior
install package then call RTMP it crashed
Version
My
package.json
{ "name": "my-app", "version": "1.0.0", "main": "index.js", "scripts": { "start": "expo start", "android": "expo run:android", "ios": "expo run:ios", "web": "expo start --web" }, "dependencies": { "@expo/vector-icons": "^13.0.0", "@jellyfish-dev/react-native-membrane-webrtc": "^7.0.2", "@react-navigation/native": "^6.1.9", "@react-navigation/native-stack": "^6.9.15", "@tamagui/config": "^1.74.21", "@tamagui/core": "^1.74.21", "expo": "~49.0.15", "expo-av": "^13.6.0", "expo-camera": "^13.6.0", "expo-dev-client": "^2.4.11", "expo-splash-screen": "^0.22.0", "expo-status-bar": "~1.6.0", "react": "18.2.0", "react-native": "0.72.6", "react-native-gesture-handler": "^2.13.3", "react-native-haptic-feedback": "^2.2.0", "react-native-keychain": "^8.1.2", "react-native-mmkv": "^2.10.2", "react-native-reanimated": "^3.5.4", "react-native-rtmp-publisher": "^0.4.7", "react-native-safe-area-context": "^4.7.3", "react-native-screens": "^3.26.0" }, "devDependencies": { "@babel/core": "^7.20.0", "@types/react": "~18.2.14", "typescript": "^5.1.3" }, "private": true }
Smartphone info.
my Device Pixel_4_XL
Additional context
No response
Screenshots
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: