我试图允许用户在反应本地应用程序中上传视频,但是甚至可以访问相机也很难。
**不使用博览会。我使用了反应的CLI,并使用了反应本机来生成我的项目**
**使用反应本版本0.53.0。Android版本5.1 **
**更新:经过一些很好的建议,我将Android/app/build.gradle文件中的CompileSdkversions和TargetsDkversions更改为> 23,并且知道问题与我的权限不在。此外,弃用的Rctcamera版本的React-Native-Native-Camera效果很好,我能够捕获静止图像和视频并将其保存到设备中。只有使用RNCamera的主版本,每次屏幕加载时仍会崩溃该应用:/
这不太理想,因为我不想在应用程序中弃用代码。因此,当我指的是下面的反应式相机时,我的意思是使用rncamera而不是rctcamera的当前版本。**
我尝试使用React-Native-Camera软件包(https://github.com/reaeact-native-community/reaeact-native-camera(,但这会导致我的应用每次崩溃。另外,我想使用用户已经安装的相机应用程序,而不是必须构建自己的相机视图,这是React-Native-native-camera所需的。
环顾四周,我偶然发现了解决此问题的三种有希望的方法:
1(链接 - 据我从此stackoverflow帖子中了解(React Native向特定的WhatsApp Number2发送消息(链接可用于打开用户在其设备上拥有的其他应用程序。我认为这也可用于访问相机应用程序。但是我还没有找到有关此信息的任何信息。如何检查用户是否具有相机应用,然后链接到它们?理想情况下,将出现在用户手机上的弹出菜单,要求用户从可用的相机应用列表中进行选择。
2(来自Android开发人员文档的这篇文章-https://developer.android.com/training/camera/videobasics.html。这描述了如何准确地做我想做的事情,但是我很难将本机模块用于组件中。我对建造桥梁的桥梁有非常基本的知识,并且只能在阅读了一些列出所有代码的文章后才能使一个简单的本机吐司模块工作。那么任何人都可以编写一个可用于实现与Android文档指定的功能相同功能的videoModule.java文件吗?这对我来说似乎是最简单的解决方案,但是我对Java/Android的了解不足。
3(ReactNativeWebrtc-我已经在应用程序中的其他屏幕上成功包含了此模块(https://github.com/oney/react-native-webrtc(。但是,当我使用此模块在两个同行之间流式视频时,它看不到如何使用它来上传视频。我看了看是否有与Mediarecorder API相似的东西,我在该应用程序的网络版本中使用了一些东西,但是我没有任何运气。但是我知道,如果我可以从媒体流中获取二进制数据,那么我可以将其直接发送给服务器。因此,是否有一种方法可以直接从GetuserMedia((方法中直接存储媒体流,该方法反应 - 网状网络在没有Mediarecorder的情况下使用像网络上的Mediarecorder?
?任何解决方案在这里都会非常有帮助。而且,由于我目前只有一部Android手机可以测试,因此我不需要如何与iOS一起工作的信息。只是一种解决方案。非常感谢。
这是我的androidmanifest.xml权限:
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<uses-permission android:name="android.permission.CAMERA" />
<uses-feature android:name="android.hardware.camera" />
<uses-feature android:name="android.hardware.camera.autofocus"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
<uses-permission android:name="android.permission.RECORD_VIDEO" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
我的android/app/build.gradle文件:
apply plugin: "com.android.application"
import com.android.build.OutputFile
/**
* The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
* and bundleReleaseJsAndAssets).
* These basically call `react-native bundle` with the correct arguments during the Android build
* cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load
the
* bundle directly from the development server. Below you can see all the possible configurations
* and their defaults. If you decide to add a configuration block, make sure to add it before the
* `apply from: "../../node_modules/react-native/react.gradle"` line.
*
* project.ext.react = [
* // the name of the generated asset file containing your JS bundle
* bundleAssetName: "index.android.bundle",
*
* // the entry file for bundle generation
* entryFile: "index.android.js",
*
* // whether to bundle JS and assets in debug mode
* bundleInDebug: false,
*
* // whether to bundle JS and assets in release mode
* bundleInRelease: true,
*
* // whether to bundle JS and assets in another build variant (if configured).
* // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
* // The configuration property can be in the following formats
* // 'bundleIn${productFlavor}${buildType}'
* // 'bundleIn${buildType}'
* // bundleInFreeDebug: true,
* // bundleInPaidRelease: true,
* // bundleInBeta: true,
*
* // whether to disable dev mode in custom build variants (by default only disabled in release)
* // for example: to disable dev mode in the staging build type (if configured)
* devDisabledInStaging: true,
* // The configuration property can be in the following formats
* // 'devDisabledIn${productFlavor}${buildType}'
* // 'devDisabledIn${buildType}'
*
* // the root of your project, i.e. where "package.json" lives
* root: "../../",
*
* // where to put the JS bundle asset in debug mode
* jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
*
* // where to put the JS bundle asset in release mode
* jsBundleDirRelease: "$buildDir/intermediates/assets/release",
*
* // where to put drawable resources / React Native assets, e.g. the ones you use via
* // require('./image.png')), in debug mode
* resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
*
* // where to put drawable resources / React Native assets, e.g. the ones you use via
* // require('./image.png')), in release mode
* resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
*
* // by default the gradle tasks are skipped if none of the JS files or assets change; this means
* // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
* // date; if you have any other folders that you want to ignore for performance reasons (gradle
* // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
* // for example, you might want to remove it from here.
* inputExcludes: ["android/**", "ios/**"],
*
* // override which node gets called and with what additional arguments
* nodeExecutableAndArgs: ["node"],
*
* // supply additional arguments to the packager
* extraPackagerArgs: []
* ]
*/
project.ext.react = [
entryFile: "index.js"
]
apply from: "../../node_modules/react-native/react.gradle"
/**
* Set this to true to create two separate APKs instead of one:
* - An APK that only works on ARM devices
* - An APK that only works on x86 devices
* The advantage is the size of the APK is reduced by about 4MB.
* Upload all the APKs to the Play Store and people will download
* the correct one based on the CPU architecture of their device.
*/
def enableSeparateBuildPerCPUArchitecture = false
/**
* Run Proguard to shrink the Java bytecode in release builds.
*/
def enableProguardInReleaseBuilds = false
android {
compileSdkVersion 26
buildToolsVersion "25.0.2"
defaultConfig {
applicationId "com.slimnative"
minSdkVersion 16
targetSdkVersion 26
versionCode 1
versionName "1.0"
ndk {
abiFilters "armeabi-v7a", "x86"
}
}
splits {
abi {
reset()
enable enableSeparateBuildPerCPUArchitecture
universalApk false // If true, also generate a universal APK
include "armeabi-v7a", "x86"
}
}
buildTypes {
release {
minifyEnabled enableProguardInReleaseBuilds
proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
}
}
// applicationVariants are e.g. debug, release
applicationVariants.all { variant ->
variant.outputs.each { output ->
// For each separate APK per architecture, set a unique version code as described here:
// http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
def versionCodes = ["armeabi-v7a":1, "x86":2]
def abi = output.getFilter(OutputFile.ABI)
if (abi != null) { // null for the universal-debug, universal-release variants
output.versionCodeOverride =
versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
}
}
}
}
dependencies {
compile fileTree(dir: "libs", include: ["*.jar"])
compile "com.android.support:appcompat-v7:23.0.1"
compile "com.facebook.react:react-native:+" // From node_modules
compile project(':WebRTCModule')
compile project(':react-native-svg')
compile (project(':react-native-camera')) {
// exclude group: "com.google.android.gms"
exclude group: "com.android.support"
}
// compile ("com.google.android.gms:play-services-vision:10.2.0") {
// force = true;
// }
compile ('com.android.support:exifinterface:26.0.1') {
force = true;
}
}
// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
from configurations.compile
into 'libs'
}
和我的android/build.gradle:
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
mavenLocal()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
maven { url "https://jitpack.io" }
maven {
url "https://maven.google.com"
}
}
}
嘿@mraaron我刚刚制作了一个我必须制作和上传视频的本机应用程序,基本上您可以使用2种方法:
1(反应本机图像拾取器 https://github.com/reaeact-community/reeact-native-image-picker 打开本地摄像机以录制视频,作为响应将给出 u路径和其他信息。该模块具有两个功能 图像和视频定义选项时,您可以指定介体类型: iOS上的"照片","视频"或"混合","照片"或"视频"
。
2(反应本机相机 https://github.com/reaeact-native-community/reeact-native-camera 您可以自定义相机窗口,因为它不会打开本机 相机应用
Note:- I have implemented both the packages and both are working absolutely fine in android as well as ios, if u need any help u can ping me up.
这是我昨天刚刚做的演示...如果有帮助:
import React from 'react';
import { View, Text, Alert } from 'react-native';
import { BarCodeScanner, Permissions } from 'expo';
class CameraForm extends React.Component {
state = {
hasCameraPermission: null
};
componentDidMount() {
this.permissionCheck();
}
permissionCheck = async () => {
const { status } = await Permissions.askAsync(Permissions.CAMERA);
this.setState({
hasCameraPermission: status === 'granted'
});
};
handleBarCodeScanRead = data => {
Alert.alert(
'Scan successful!',
JSON.stringify(data)
);
};
render() {
return (
<View style={styles.container}>
<Text>Scan your wallet code</Text>
{ this.state.hasCameraPermission === null ?
<Text>Requesting for camera permission</Text> :
this.state.hasCameraPermission === false ?
<Text>Camera permission is not granted</Text> :
<BarCodeScanner
onBarCodeRead={this.handleBarCodeScanRead}
style={{ height: 400, width: 400, marginTop: 20 }}
/>
}
</View>
);
}
}
const styles = {
container: {
flex: 1,
alignSelf: 'stretch',
alignItems: 'center',
justifyContent: 'center',
backgroundColor: 'white'
}
};
export default CameraForm
;
关于应用程序每次崩溃,您是否仔细检查了您在AndroidManifest.xml/info.plist中提到了应用程序所需的所有权限吗?
另外,您希望将外部应用用于相机视图的特定原因是什么?因为我已经使用了反应式相机,并且它可以无缝地工作。