I'm using VS2015 Update 2 with TACO Update 9 and I'm attempting to debug an application on a iPhone 6S (iOS 9.3.1) attached to my Windows computer. The remote build is successful but I get the following messages when it attempts to debug the app:
2>------ Deploy started: Project: xyz, Configuration: Debug iOS ------
2>Found iTunes version: 12.3.0.44
2>Uninstalling app ID: com.bob.xyz.
2>Successfully installed .ipa file: D:\Documents\Projects\xyz\xyz\bin\iOS\Debug\xyz.ipa.
2>Starting idevicedebugserverproxy.exe at port 3000.
2>Cannot find the app installed on the device. Check that the device is connected, awake, and unlocked.
2>Deployment failed.
When I look on the device, I do not see the application. Are there steps I can take to further debug what might be causing the failure?
Make sure your solution is configured for Debug build and not Release.
Related
After update to Android Studio Arctic Fox 2020.3.1 Patch 4,
Error: Could not resolve aapt2-7.0.4-7396180-windows.jar (com.android.tools.build:aapt2:7.0.4-7396180): No cached version
Execution failed for task ':app:processDebugResources'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Failed to transform viewbinding-7.0.4.aar (androidx.databinding:viewbinding:7.0.4) to match attributes {artifactType=android-compiled-dependencies-resources, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}.
.
.
Possible solution:
- Disable offline mode and rerun the build
if I disable offline mode and syn the project again. Then even its not building the project then errors comes again.
Error after disabling offline mode:
:app:writeDebugSigningConfigVersions
FAILURE: Build completed with 8 failures.
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:dataBindingMergeDependencyArtifactsDebug'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Could not resolve com.cuberto:liquid-swipe:1.0.0.
Required by:
project :app
> Could not resolve com.cuberto:liquid-swipe:1.0.0.
> Could not get resource 'https://dl.bintray.com/amulyakhare/maven/com/cuberto/liquid-swipe/1.0.0/liquid-swipe-1.0.0.pom'.
> Could not HEAD 'https://dl.bintray.com/amulyakhare/maven/com/cuberto/liquid-swipe/1.0.0/liquid-swipe-1.0.0.pom'. Received status code 502 from server: Bad Gateway
.
many errors
.
.
Could not HEAD 'https://dl.bintray.com/amulyakhare/maven/com/cuberto/liquid-swipe/1.0.0/liquid-swipe-1.0.0.pom'. Received status code 502 from server: Bad Gateway
Disable Gradle 'offline mode' and sync project
even offline mode is deactivated.
What's wrong with it?
Even Firebase is not connecting to internet through firebase Assistant though Android Studio.
I found the culprit for this in my project.
Earlier I was using in all projects repositories in build.gradle(Exam String)
maven {
url 'https://dl.bintray.com/amulyakhare/maven'
}
In earlier Android studio versions, it was working using this repositories.
After removing this from build.gradle(Exam String).
It started working fine.
It is used for liquide swipe view pager.
For reference I have added screenshot of repositories.
I am trying to deploy my application built in ASP.Net 4.6.1. So I am using HWC Buildpack.
Below is my manifest.yml
---
applications:
- name: DRSN
random-route: true
memory: 128M
buildpack:
https://github.com/cloudfoundry/hwc-buildpack.git
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
The error that I am receiving is below.
Waiting for API to complete processing files...
Staging app and tracing logs...
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 creating container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 successfully created container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (231B)
Downloaded app package (19.5M)
Failed to compile droplet: Failed to compile droplet: fork/exec /tmp/buildpackdownloads/6c6dca8d638ac0d145d6581f9eb9a96a/bin/compile: permission denied
Exit status 223
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 stopping instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 destroying container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Error staging application: App staging failed in the buildpack compile phase
Can anyone help me resolve this issue? Am I not correct in my manifest.yml? Or is it something else?
I believe that the problem is that you're telling the system to use the HWC buildpack, but at the same time you're not setting the Windows stack (at least based on what info I can see). That means it's going to default to the Linux stack, which I believe is why you're seeing the fork/exec /tmp/buildpackdownloads/... error.
Try adding stack: windows to your manifest.yml or -s windows to your cf push command (for future reference, when you need help always include the full cf push command you're running).
PS: you shouldn't use https://github.com/cloudfoundry/hwc-buildpack.git that is telling the system to grab the master branch in whatever state it's currently in. That's a.) not reproducible and b.) not guaranteed to be in a working state. You should either use the platform provided buildpack names (from cf buildpacks) or append #<branch_or_tag> to the end of the URL so it picks a specific branch. All CF Buildpacks have tags for each release. It's strongly recommended you use a tagged release.
I started porting my Flutter app to macos Desktop. The UI started fine. However, as soon as the app makes a network call, it fails instantly with Connection failed (OS Error: Operation not permitted).
Running a one-liner:
final response = await http.get('https://jsonplaceholder.typicode.com/posts/1');
fails with:
Unhandled Exception: SocketException: Connection failed (OS Error:
Operation not permitted, errno = 1),
address = jsonplaceholder.typicode.com, port = 443
#0 IOClient.send (package:http/src/io_client.dart:33:23)
The macos build target comes from Google's sample here.
Flutter (Channel master, v1.9.8-pre.108)
Per my comment on the other answer, you should not use the Xcode capabilities UI for this. It will not correctly handle the two separate entitlement files in a Flutter project.
You need to add:
<key>com.apple.security.network.client</key>
<true/>
to macos/Runner/DebugProfile.entitlements and macos/Runner/Release.entitlements.
This is documented here and here.
Your macOS XCode project lacks Internet permission called "Outgoing Connections (Client)".
Open your macos xcode project - [root]/macos/Runner.xcworkspace
Click "Runner" in Project navigator - general settings will show up. Select "Capabilities" from tabbar and tick option "Outgoing Connections (Client)".
Rebuild your application inside XCode and launch the project.
If you are getting this error Only in Android release then Internet permission must be missing from main manifest. You just need to add Internet permission in Manifest file.
Just add this permission in manifest <uses-permission android:name="android.permission.INTERNET"/>
There are three manifest file available in Android folder
app/src/debug
app/src/main
app/src/profile
I m having 2 version of VS2017 and a mac with latest macOS.
I transfer my Xamarin forms App file from VS2017 enterprise to a machine(more than 3 years old but running win10 pro) with VS2017 Community version. When I debug ( with selecting Android project and VS-android-23 X86 tablet as emulator ) this App in VS2017 Community version , I have no compilation error but have these message:
Found conflicts between different versions of the same dependent assembly
that could not be resolved.
These reference conflicts are listed in the build log when log verbosity is set to detailed.
I could not understand this message. I have no problem running the same app in VS2017 Enterprize ver but I have this error message in VS2017 Community ver.
Update
Click View > Output --> this will show the error
1>Starting deploy VisualStudio_android-23_x86_tablet ...
1>Starting emulator VisualStudio_android-23_x86_tablet ...
1>C:\Users\xxxxx\AppData\Local\Android\ANDROI~1\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd VisualStudio_android-23_x86_tablet -prop monodroid.avdname=VisualStudio_android-23_x86_tablet
1>emulator: ERROR: x86 emulation currently requires hardware acceleration!
1>Please ensure Intel HAXM is properly installed and usable.
1>CPU acceleration status: Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.
1>Emulator VisualStudio_android-23_x86_tablet cannot be started.
Please help.
Recently installed VS 2015 Community Update 3 in Windows 10 Pro 32 bit. For the past couple days I have been playing with Cordova, but can not get it to work correctly.
I tried:
Redirect index.html hack.
Clearing cache in TACO settings
Repaired VS
This text is from the build log / VS / emulator / debug log / me.
Build: Warning: No emulator specified, defaulting to AVD_GalaxyNexus_ToolsForApacheCordova
Build: Failed to create Context 0x3005
VS: There were deployment errors. Continue?
Me: If I click Yes
Build: Debug is starting
Emulator: "The connection to the server was unsuccessful. (file:///android_assset/www/index.html)"
Me: App appears 3 times on emulator
Me: Breakpoints don't work. In the Debug log I see many messages "Cannot find or open the PDB file."
Me: Build log says the app was installed but Deploy failed?
Build:
Installing apk C:/Users/pears/Documents/Visual Studio 2015/Projects/BlankCordovaApp1/platforms/android/build/outputs/apk/android-debug.apk on emulator-5554...
INSTALL SUCCESS
Unlocking screen...
Running command "input keyevent 82" on emulator-5554...
Starting application "io.cordova.myapp6178b0/.MainActivity" on emulator-5554...
Running command "am start -W -a android.intent.action.MAIN -nio.cordova.myapp6178b0/.MainActivity" on emulator-5554...
LAUNCH SUCCESS
Executing "after_run" hook for all plugins.
Warning: No emulator specified, defaulting to AVD_GalaxyNexus_ToolsForApacheCordova
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Me: I don't see any errors in the build log.
Update 7.22.2016
I created a new Azure VM (Windows 2012 R2 Datacenter, 64 bit, 2 core Intel 2.2, 7 GB RAM) and installed VS 2015 and Cordova. From the AVD manager, the base emulator started up fine. However, the deploy still failed for a blank Cordova project. I saw the white Cordova screen saying it was connecting to device. Then the same message "The connection to the server was unsuccessful. (file:///android_assset/www/index.html)". Maybe the Redirect index.html hack will help. I didn't try.
Next, I Installed the stand-alone Android Studio in my desktop Windows 10 VM for more options with the AVD and SDK. Immediately, it tells me my CPU doesn't support VT-x. Makes sense - it's an AMD processor. I started the AVD GalaxyNexus ToolsForApacheCordova emulator anyway and it never finished loading. It targets API 19, Android 4.4, and arm CPU. I tried upgrading to API 23 which refused to run and says:
Intel HAXM is required to run this AVD.
Your CPU does not support required features (VT-x or SVM).
Unfortunately, your computer does not support hardware accelerated virtualization.
Here are some of your options:
1) Use a physcal device for testing
2) Develop on a Windows/OSX computer with an Intel processor that supports VT-x and NX
3) Develop on a Linux computer that supports VT-x or SVM
4) Use an Android Virtual Device based on an ARM system image
(This is 10x slower than hardward accelerated virtualization)
It seems like VS failed to create an Android Virtual Device. You can create one in the version of Android Studio that VS installs on your machine. The default location is in "C:\Users[usename]\AppData\Local\Android\sdk\". Click on "Avd Manager" and create a device. Make sure its the only device created--any existing ones may be broken. Then, go back to VS and click "Android -> Build to Google Android emulator".
FYI--if you have Hyper V enabled (you are using a Windows Phone emulator), you should be selecting the ARM system image.