- Java 双重比较
- java - 比较器与 Apache BeanComparator
- Objective-C 完成 block 导致额外的方法调用?
- database - RESTful URI 是否应该公开数据库主键?
我正在尝试使用我的手机进行原生 react 。但我得到一个奇怪的错误,似乎无法解决它。有人可以帮忙吗?这是堆栈跟踪:
<everything fine above>
:app:validateSigningDebug
:app:packageDebug UP-TO-DATE
:app:assembleDebug UP-TO-DATE
:app:installDebug
Installing APK 'app-debug.apk' on 'Aqua 4G+ - 5.0' for app:debug
Unable to install C:\Users\Mehul\Desktop\app\android\app\build\outputs\apk\app-debug.apk
com.android.ddmlib.InstallException: Failed to install all
at com.android.ddmlib.SplitApkInstaller.install(SplitApkInstaller.java:89)
at com.android.ddmlib.Device.installPackages(Device.java:904)
at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:137)
at com.android.build.gradle.internal.tasks.InstallVariantTas
<some more java errors>
02:58:27 E/427709463: Error while uploading app-debug.apk : Unknown failure ([CDS]close[0])
:app:installDebug FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:installDebug'.
> com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: Failed to install all
我只包含了必要的堆栈,以便于阅读。
最佳答案
I had to type:
adb kill-server
Wait a moment then run:
adb devices
In my case output is like are as follows
**List of Devices Attached**
*0123456789ABCDEF device*
This will show you the DEVICE_ID (0123456789ABCDEF) of your device running android.
then you will have to run below command and make sure usb is enabled
react-native run-android --deviceId 0123456789ABCDEF
After that my output be like
**D:\React\albums>adb devices
List of devices attached
0123456789ABCDEF device
D:\React\albums>react-native run-android --deviceId 0123456789ABCDEF
Scanning 636 folders for symlinks in D:\React\albums\node_modules (21ms)
JS server already running.
Building the app...
Observed package id 'build-tools;23.0.1' in inconsistent location 'D:\Android\Sd
k\build-tools\build-tools-23.0.1' (Expected 'D:\Android\Sdk\build-tools\23.0.1')
Already observed package id 'build-tools;23.0.1' in 'D:\Android\Sdk\build-tools\
23.0.1'. Skipping duplicate at 'D:\Android\Sdk\build-tools\build-tools-23.0.1'
Observed package id 'extras;google;m2repository' in inconsistent location 'D:\An
droid\Sdk\extras\google\m2repository.backup' (Expected 'D:\Android\Sdk\extras\go
ogle\m2repository')
Already observed package id 'extras;google;m2repository' in 'D:\Android\Sdk\extr
as\google\m2repository'. Skipping duplicate at 'D:\Android\Sdk\extras\google\m2r
epository.backup'
Observed package id 'system-images;android-24;google_apis;x86' in inconsistent l
ocation 'D:\Android\Sdk\system-images\android-24\google_apis\x86.backup' (Expect
ed 'D:\Android\Sdk\system-images\android-24\google_apis\x86')
Already observed package id 'system-images;android-24;google_apis;x86' in 'D:\An
droid\Sdk\system-images\android-24\google_apis\x86'. Skipping duplicate at 'D:\A
ndroid\Sdk\system-images\android-24\google_apis\x86.backup'
Observed package id 'build-tools;23.0.1' in inconsistent location 'D:\Android\Sd
k\build-tools\build-tools-23.0.1' (Expected 'D:\Android\Sdk\build-tools\23.0.1')
Already observed package id 'build-tools;23.0.1' in 'D:\Android\Sdk\build-tools\
23.0.1'. Skipping duplicate at 'D:\Android\Sdk\build-tools\build-tools-23.0.1'
Observed package id 'extras;google;m2repository' in inconsistent location 'D:\An
droid\Sdk\extras\google\m2repository.backup' (Expected 'D:\Android\Sdk\extras\go
ogle\m2repository')
Already observed package id 'extras;google;m2repository' in 'D:\Android\Sdk\extr
as\google\m2repository'. Skipping duplicate at 'D:\Android\Sdk\extras\google\m2r
epository.backup'
Observed package id 'system-images;android-24;google_apis;x86' in inconsistent l
ocation 'D:\Android\Sdk\system-images\android-24\google_apis\x86.backup' (Expect
ed 'D:\Android\Sdk\system-images\android-24\google_apis\x86')
Already observed package id 'system-images;android-24;google_apis;x86' in 'D:\An
droid\Sdk\system-images\android-24\google_apis\x86'. Skipping duplicate at 'D:\A
ndroid\Sdk\system-images\android-24\google_apis\x86.backup'
Incremental java compilation is an incubating feature.
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareComAndroidSupportAppcompatV72301Library UP-TO-DATE
:app:prepareComAndroidSupportSupportV42301Library UP-TO-DATE
:app:prepareComFacebookFbuiTextlayoutbuilderTextlayoutbuilder100Library UP-TO-DA
TE
:app:prepareComFacebookFrescoDrawee101Library UP-TO-DATE
:app:prepareComFacebookFrescoFbcore101Library UP-TO-DATE
:app:prepareComFacebookFrescoFresco101Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipeline101Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipelineBase101Library UP-TO-DATE
:app:prepareComFacebookFrescoImagepipelineOkhttp3101Library UP-TO-DATE
:app:prepareComFacebookReactReactNative0451Library UP-TO-DATE
:app:prepareComFacebookSoloaderSoloader010Library UP-TO-DATE
:app:prepareOrgWebkitAndroidJscR174650Library UP-TO-DATE
:app:prepareDebugDependencies
:app:compileDebugAidl UP-TO-DATE
:app:compileDebugRenderscript UP-TO-DATE
:app:generateDebugBuildConfig UP-TO-DATE
:app:mergeDebugShaders UP-TO-DATE
:app:compileDebugShaders UP-TO-DATE
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets UP-TO-DATE
:app:generateDebugResValues UP-TO-DATE
:app:generateDebugResources UP-TO-DATE
:app:mergeDebugResources UP-TO-DATE
:app:bundleDebugJsAndAssets SKIPPED
:app:processDebugManifest UP-TO-DATE
:app:processDebugResources UP-TO-DATE
:app:generateDebugSources UP-TO-DATE
:app:incrementalDebugJavaCompilationSafeguard UP-TO-DATE
:app:compileDebugJavaWithJavac UP-TO-DATE
:app:compileDebugNdk UP-TO-DATE
:app:compileDebugSources UP-TO-DATE
:app:transformClassesWithDexForDebug UP-TO-DATE
:app:mergeDebugJniLibFolders UP-TO-DATE
:app:transformNative_libsWithMergeJniLibsForDebug UP-TO-DATE
:app:processDebugJavaRes UP-TO-DATE
:app:transformResourcesWithMergeJavaResForDebug UP-TO-DATE
:app:validateSigningDebug
:app:packageDebug UP-TO-DATE
:app:assembleDebug UP-TO-DATE
:app:checkReleaseManifest
:app:prepareReleaseDependencies
:app:compileReleaseAidl UP-TO-DATE
:app:compileReleaseRenderscript UP-TO-DATE
:app:generateReleaseBuildConfig UP-TO-DATE
:app:mergeReleaseShaders UP-TO-DATE
:app:compileReleaseShaders UP-TO-DATE
:app:generateReleaseAssets UP-TO-DATE
:app:mergeReleaseAssets UP-TO-DATE
:app:generateReleaseResValues UP-TO-DATE
:app:generateReleaseResources UP-TO-DATE
:app:mergeReleaseResources UP-TO-DATE
:app:bundleReleaseJsAndAssets UP-TO-DATE
:app:processReleaseManifest UP-TO-DATE
:app:processReleaseResources UP-TO-DATE
:app:generateReleaseSources UP-TO-DATE
:app:incrementalReleaseJavaCompilationSafeguard UP-TO-DATE
:app:compileReleaseJavaWithJavac UP-TO-DATE
:app:compileReleaseNdk UP-TO-DATE
:app:compileReleaseSources UP-TO-DATE
:app:lintVitalRelease
:app:transformClassesWithDexForRelease UP-TO-DATE
:app:mergeReleaseJniLibFolders UP-TO-DATE
:app:transformNative_libsWithMergeJniLibsForRelease UP-TO-DATE
:app:processReleaseJavaRes UP-TO-DATE
:app:transformResourcesWithMergeJavaResForRelease UP-TO-DATE
:app:packageRelease UP-TO-DATE
:app:assembleRelease
:app:assemble
:app:incrementalDebugUnitTestJavaCompilationSafeguard UP-TO-DATE
:app:preDebugUnitTestBuild UP-TO-DATE
:app:prepareDebugUnitTestDependencies
:app:compileDebugUnitTestJavaWithJavac UP-TO-DATE
:app:processDebugUnitTestJavaRes UP-TO-DATE
:app:compileDebugUnitTestSources UP-TO-DATE
:app:mockableAndroidJar UP-TO-DATE
:app:assembleDebugUnitTest UP-TO-DATE
:app:testDebugUnitTest UP-TO-DATE
:app:incrementalReleaseUnitTestJavaCompilationSafeguard UP-TO-DATE
:app:preReleaseUnitTestBuild UP-TO-DATE
:app:prepareReleaseUnitTestDependencies
:app:compileReleaseUnitTestJavaWithJavac UP-TO-DATE
:app:processReleaseUnitTestJavaRes UP-TO-DATE
:app:compileReleaseUnitTestSources UP-TO-DATE
:app:assembleReleaseUnitTest UP-TO-DATE
:app:testReleaseUnitTest UP-TO-DATE
:app:test UP-TO-DATE
:app:check
:app:build
BUILD SUCCESSFUL
Total time: 16.717 secs
Running D:\Android\Sdk/platform-tools/adb -s 0123456789ABCDEF reverse tcp:8081 t
cp:8081
Installing the app on the device (cd android && adb -s 0123456789ABCDEF install
app/build/outputs/apk/app-debug.apk
app/build/outputs/apk/app-debug.apk: 1...ed. 3.2 MB/s (8067631 bytes in 2.442s)
pkg: /data/local/tmp/app-debug.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Starting the app on 0123456789ABCDEF (D:\Android\Sdk/platform-tools/adb -s 01234
56789ABCDEF shell am start -n com.albums/com.albums.MainActivity)...
Starting: Intent { cmp=com.albums/.MainActivity }
**
The important part was the --deviceId XYZ. Without this, the apk would never get uploaded to the phone.
**First Way**
*** If you are using Latest version of React then shake your real device and press reload (In my case react-native cli version is 2.0.1 And react-native version 0.45.1 ) Dont put any machine address and port in dev setting ok ***
**if first method does not works then follow second method**
**Second Way**
Then, the app launched with a red screen... i had to shake it, dev settings, adjust the "debug server host & port for device", putting my computer's IP address and port, like this:
192.168.0.15:8081
Lastly, i had to shake my phone again and select RELOAD...
关于android - 无法使用真实设备进行 react 开发,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/43606793/
iphone设备UDID、iphone设备ID和iphone设备Token之间有什么区别? 通常,当我们使用苹果推送通知服务时,会使用 iPhone 设备 token 。 但我的目标只是识别唯一的 i
我们使用 firebase 从服务器向 Android 和 IOS 设备发送通知,并且我们使用旧版 FCM 发送通知。但是当我们的应用程序在后台时,通知由系统本身处理,因此我们无法通过应用程序处理它。
在 Google 上搜索后,我发现人们说只能通过“MFi 程序”将 iOS 设备与非 iOS 设备连接起来。这是真的吗? 我的项目主要集中于直接通过蓝牙与Arduino设备发送和接收信息。 iOS和非
所以我有一个通用应用程序,我正在设置 UIScrollView 的内容大小。显然,iPhone 和 iPad 上的内容大小会有所不同。如何为 iPad 设置某种尺寸,为 iPhone 和 iPod t
问题:如何在 pod 中使用连接到主机的原始设备作为 block 设备。 我尝试使用类型为“BlockDevice”的“hostPath” volumes: - my-data: hostPath
Implemented GCKDeviceScannerListener Singleton Class on ViewController, however its delegate methods
我有一个 (PhoneGap) 应用程序,它将成功获得 Passbook 通行证,并且还将成功接收与 Passbook 分开的推送通知(当伪造设备 ID 时)。 我遇到的问题是发送给注册设备的设备 I
我正在尝试找到一种方法,通过我目前正在使用的 iOS 应用程序访问我的信标的电池电量。我正在使用 Kontakt 的 iBeacon 设备。我浏览了 Estimote iOS SDK,他们提供了一种实
我正在努力让 CUDA 应用程序也能监控 GPU 的核心温度。可通过 NVAPI 访问该信息。 问题是我想确保在运行代码时监控的是同一个 GPU。 但是,似乎有信息表明我从 NvAPI_EnumPhy
从沙箱模式到生产模式,设备 token 有何不同? 我认为我已将一些设备 token 锁定为生产模式,并且无法将它们从开发中插入。 关于如何检查有什么想法吗? 最佳答案 当您使用开发证书构建应用程序时
目录 /run/user/1000/gvfs 和 ~/.gvfs 分别是空的和不存在的。我的图形文件管理器 (Thunar) 能够检测和访问设备的内部和外部存储器。 命令 gvfs-mount -l
我有一个 Android 平板电脑,它有一个迷你 USB 端口和一个 USB 端口,我想编写一个与 USB key 通信的应用程序。我写了一个demo来找出U盘,但是没有任何反应。 令我不安的是,如果
我们将 PHP 版本从 5.4.25 更改为 5.4.45,并在服务器上安装了 MS SQL 驱动程序。在更改服务器之前,一切正常,但在更改服务器之后,我遇到了 Web 服务问题。我们的身份验证 So
我想知道是否有人使用此 API 在 Android 设备上同时从 2 个后置摄像头捕获图像或视频:https://source.android.com/docs/core/camera/concurr
我正在为客户构建一个物联网解决方案,网络管理员坚持要求设备仅通过访客网络进行连接,该网络有一个强制门户,其中的服务条款必须通过按下 UI 按钮来接受,然后才能获得外部互联网访问。到目前为止,我见过的大
我无法弄清楚这里的格式规则..在我的示例中,代码行太多,无法为每行添加 4 个空格,因此这里是我需要帮助的代码的链接 http://nitemsg.blogspot.com/2011/01/heres
如果我在我的设备上接受推送通知,并且不保存设备 token ,那么我如何在自定义 View 中查看设备 token 或恢复警报 View ? 我删除了应用程序并重新安装,但看不到设备 token 警报
我试图找出在尝试并行比较和复制设备 block 与 pthreads 时我做错了什么。看起来我正在脱离同步并且比较阶段无法正常工作。任何帮助将不胜感激 #ifndef __dbg_h__ #defin
我刚刚写完所有这些内容,但这个红色的小栏告诉我我不能发布图片或两个以上的链接。因此,如果您可以引用 this Imgur album , 那简直太好了。谢谢。 我在这里相对较新,甚至对 android
我需要启用 mysql 常规日志并将其通过 nsf 移动到我系统中的另一个驱动器/设备! 所以,我在 my.cnf 中启用了它: general_log = 1 general_log_fi
我是一名优秀的程序员,十分优秀!