When I try to run my xamarin.iOS project in some devices it says .. upload succeeded and app get disconnected from visual studio but my expectation is I should be able to debug the app from visual studio.
This doesn't happen with all devices.
I verified there is no code signer or provisioning profile problem with these devices.
Any ideas on how to solve this issue (I am using visual studio 2017 for mac )
Clear the temp files
Restart the mac
solved
Related
I'm new to xamarin. I wrote a simple "Hello World" app using VS 2019 on Windows 10 which runs successfully on the emulators. I have an iMAC on my network and it is successfully connected to my Windows visual studio on Win10 machine. No update warnings or mismatch version error message(s) during the paring of the Windows VS to the remote iMac. On my list of emulators, I have a long list of emulators and "Remote Device" option. All in all, all is well when I work with the emulators.
Now, when I connect my iPhone XR (iOS 13.4.1) using USB to my VS 2019 on Win10, the expected result would be that my device would show up along side of all the emulators so that I can deploy to the device for debugging. My first question is whether or not that is the right assumption. If it is, then in my case that doesn't happen. When I start iTunes program on my Windows machine, it has no issues connecting to my iphone (I can do backup, restore, etc.). Interestingly, in VS, the Device Log has no issues connecting to the connected iphone either. My phone is listed on the drop down box on the top left hand corner of the screen. At this point, I can only assume that is not a connection issue.
What I'm left with is some kind of mismatch setting on VS 2019 in Win10 or on my connected iphone that is causing VS 2019 on win10 not seeing my usb-connected iphone. Any ideas what setting I should fiddle around with? Thanks in advance.
First option, you need to connect iPhone over USB on Mac device , then you can debug in iPhone device .
Second option ,If Mac device not always around you , you also can connect to iPhone device Over Wifi .
An important part of the developer workflow is deploying to a device. Xcode 9 introduced the option of deploying to an iOS device or Apple TV through a network, rather than having to hardwire your devices every time you want to deploy and debug your app. This feature has been introduced in Visual Studio for Mac 7.4 and Visual Studio 15.6 release.
This guide details how to pair and deploy to a device over the network : https://learn.microsoft.com/en-us/xamarin/ios/deploy-test/wireless-deployment?tabs=windows
Ok, so what you need to do is select "Debug|iPhone" or "Release|iPhone" from the build configuration menu.
I am running the latest version of Visual Studio and the latest version of unity. When I open the project using Visual Studio for Mac, I am able to rebuild the app.
But, when I try to start debugging, I am getting Execution Failed without any explanation or build output.
I am able to run the app successfully on iOS through Xcode, although the iPad is refusing to start the app automatically and I have to open it manually.
The issue is that , I can't start the app on Visual Studio for Mac.
Apparently, If you open multiple instances of Unity, Visual Studio for Mac will get confused and will not know which project to attach to.
Having one instance solved the issue for me.
I am trying to generate the ipa file in order to publish it to the Apple Store but Visual Studio (2015 Community Edition) doesn't create it.
I followed the steps from the official Xamarin docs but it doesn't work, I tried selecting "AdHoc", "Release" and "AppStore" (with iPhone platform selected), I have the last Xamarin updates in my Windows and Mac build hosts, the build process ends succesfully but the ipa file doesn't appear in the **Bin > iPhone > Ad Hoc (or Release) folder.
I am using the distribution profile.
I would really appreciate any help.
A combination of clearing the bin/iPhone/Ad-Hoc folder, changing the build number, restarting Visual Studio, and re-connecting to the Mac resolved this for me.
I wanted to test out the Visual Studio Emulator for Android, so I grabbed an example project (https://code.msdn.microsoft.com/hello-jni-Android-790ab73d#content). Unfortunately, I can only select 'No devices available' respectively 'Android Virtual Device Manager" under Target Device.
When I start the emulator from the menu (Extras - Visual Studio Emulator for Android), it works fine - Visual Studio just somehow can't see it.
I tried to restart VS while the Emulator was running, but that also didn't help.
adb devices -l correctly lists the running emulator, btw.
Does somebody have any idea what could be wrong?
I had the same type of issue on my environment. I checked registry key "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools" location and "Android SDK Tools" Key didn't exist. I created the Key and add String Value called Path and I provided Android SDK Tools path. It solved my issue. It is worth to shot.
Turns out I didn't get the message that the emulator only supports the debugging of x86 images - I changed the target platform to x86 and now it is working.
(Btw, I very quickly got the answer from a friendly Microsoft Employee after I sent them an email - Worth mentioning, I'd reckon)
I have created a blank Android Native C++ project using Visual Studio 2015 Preview. When I click to run it on the emulator, the emulator will load but I always get the following error and cannot run the app on the emulator.
3>Starting emulator...
3>Error installing the package. The device '169.254.191.177:5555' is invalid or not running. Please switch to another device, or use the Android Virtual Device (AVD) Manager to start a compatible emulator, or connect a compatible Android device.
3>The device is invalid or is not running.
Would this be because I have the Windows Phone emulator installed ? I havnt done anything except install Visual Studio 2015, create project, and run.
Short answer: you need to use "adb connect 169.254.191.177:5555"
Long answer:
Visual Studio 2015 Android Emulator issue
This is not likely to be a result of having the Windows Phone Emulator installed. More likely is that there is a problem with the connection between the VS Android Emulator and Visual Studio. Repairing your VS and VS Emulator for Android installations by going to Control Panel > Programs and Features may resolve this.