Sometimes, when I start debugging of android application in Visual Studio 2012 I can't see emulator image in select device window:
but emulator is already running:
The thing is that the problem is not in my application code or project settings because when i select Start emulator image, and new android virtual device is running, my application deploys successfully and is running correctly on NEW virtual device, BUT it takes a lot of time to load this new virtual device image and deploy application on it. Why doesn't Select device manages see already running virtual device image?
P.S. I deploy the simplest hello world activity, which is created by default when I start new Android Application project in Visual Studio 2012
This happens frequently.
From my informal experience... It seems sometimes to be related to VS and MonoDroid - but mostly it seems down to the Android SDK.
As the comment above suggests, switching VS off and on again can sometimes help.
Other things that can help are:
update to the latest version of Mono for Android - the Monkeys at Xamarin have added a Refresh button to the display
try using the command line adb tool in the SDK. This Android Debug Bridge includes kill-server and start-server switches - using these allows you to refresh the Android SDK's connections to devices.
For more on adb, see http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/ and http://developer.android.com/tools/help/adb.html - it's a useful tool to know
If you do identify any clear bug in Mono for Android's connectivity, then please report it on http://bugzilla.xamarin.com
Related
I'm building a Xamarin app, and, so far, I've been able to build without issue on the iPhone Simulator, but I haven't been able to get the app to launch successfully on a physical iPhone device. In the past (about a month ago), the app was working fine on the same device. Here's some background on the specifics:
I develop my Xamarin code on my Windows machine, which is linked a remote Mac (hosted by MacStadium, a third-party hosting service).
My test phone is an iPhone 5c running iOS 10.3.3
To deploy to my iPhone, I build my app in Release mode in Visual Studio, upload the code to a third-party app installation service, Installr, which hosts the IPA file and assists with the installation of my app on the physical device. I've never had an issue with Installr and have no reason to believe that this is the source of my problem.
Since the last time the app worked on the physical device, I updated Visual Studio to version 16.3.2 and updated Xamarin. Here's the Xamarin Specs:
Generally, what happens, is that I download and install my app on the iPhone without any issue. However, when I click on the app, the splash screen loads for about 5 seconds, a white screen briefly appears as follow, then the app crashes.
I've seen several related articles on StackOverflow and other sources on the internet, but none of the proposed solutions see to work for me. For example, I've tried adding [assembly: XamlCompilation(XamlCompilationOptions.Compile)]
to App.xaml.cs with no luck.
I've also played around with changing the CSProj file settings to compile for various combinations of ARM64 and ARMv7. Changing this didn't help either. I've tried changing the linker behavior to "Don't Link" from "Link Framework SDKs Only", and I get an error message stating that the native code is too large for 32-bit architectures. I would compile for only 64-architectures to get around this error, but I believe that the iPhone 5c uses a 32-bit architecture.
Here's what my iOS Project's CSProj file looks like currently. I've tried checking just about all of those checkboxes with no luck:
I'm stumped as to what this could be. Any suggestions would be greatly appreciated. To further complicate things, I haven't been able to get a good log file from the iPhone. Since the Mac is remotely hosted, I can't plug my phone into XCode to pull the logs that way. Does anyone have a reliable solution to get log files another way?
It looks like upgrading solved the problem. Visual Studio was updated to Visual Studio to 16.3.5 from 16.3.2. XCode on my Mac was updated to Version 11.1. After these updates, Visual Studio performed an update while connecting to the Mac remotely.
Our company has a native iOS app that was built in Xamarin/Visual Studio. We originally uploaded it to the App Store a few years ago and have made a few changes to it over the years.
The app itself is very basic. It's basically just a web view that navigates to a Single Page Application. There is very little native app code in the project.
Every week or so I regular launch the native app on our company iPad. Instead of running a version pulled down from the App Store, I periodically rebuild and upload the app from a Mac Mini running Visual Studio and/or debug it directly from the Mac Mini through Visual Studio.
A few days ago I tried launching the native app and after opening it immediately closed. I tried rebooting the iPad but the app still minimizes/closes immediately after opening. If I double-tab the Home button on the iPad, I can see the app still running in the background, but any time I tap on it it immediately minimizes itself.
I tried Cleaning and Rebuilding the native app solution in Visual Studio and re-uploading it to the iPad and that didn't fix it. I updated Visual Studio (and all of its packages) on the Mac Mini, updated XCode, updated Mac OS, updated iOS on the iPad, and nothing resolved the issue.
When I attempt to debug the app from Visual Studio, it shows two error codes in the Output window: MT1043 and MT1007. The debugger always fails to attach to the app as well.
I've tried Googling the error codes and the problem itself and haven't found anything that has worked. I've tried generating a new Development Certificate and Provisioning Profile to use to sign the app when uploading it to the iPad but that didn't work either.
What's strange is that if I download the app off of the App Store it works just fine. The source code that I'm attempting to build/run right now is identical to what it was at the time it was deployed to the app store. What else is strange is that, if I spin up an iOS Emulator and upload/debug against that, the app works just fine.
I tried using a different iPad and it had the same issue. The app minimizes itself immediately after attempting to launch it.
Found the answer. Had to set the system certificate trust from "Always Trust" to "Use System Default". Same solution as provided here: https://stackoverflow.com/a/52506186/9704484
I've been having this problem for a few days, and can't find any solution.
I made my app with Xamarin Studio. I am trying to upload an update for my it to iTunes Connect through Xcode. But when trying to validate the app I get the following error: "This bundle is invalid. New apps and app updates submitted to the App Store must be built with public." Dissecting this error it makes it sound like it thinks I'm using a beta SDK, which I'm not (full system specs below). Even weirder is that if I go through Xamarin Studio's Archive validation it tells me everything is fine. But when I go through Application Loader it tells me the following:
"ERROR ITMS-9000: This bundle is invalid. New apps and app updates submitted to the App Store must be built with public (GM) versions of Xcode 5.1.1 or higher and iOS 7 SDK. Do not submit apps built with beta software." Obviously this is the same error as before, just a little more detailed. But the system specs it outlines, are exactly the same as I am using.
Hopefully someone out there can lend me a hand! :D
System Specs:
Mac OSX 10.9.3
Xcode 5.1.1 (Downloaded from the Mac App Store)
iOS 7 SDK, building for iOS 7.1
Xamarin Studio 5.0
Application Loader 2.9.1
Thanks in advance!
Open your project in Xamarin Studio, then double click on Info.plist. Click on Use Asset Catalogs for both sections: Universal Icons & Universal Launch Images. It should create two new folders:
Resources/Images.xassets/AppIcons.appiconset
Resources/Images.xassets/LanuchImage.lanuchimage
Go to AppIcons.appiconset folder and make sure that you have the following file names:
AppIcon57x57.png
AppIcon57x57#2x.png
AppIcon72x72#2x~.png
AppIcon72x72~ipad.png
Rename your icons if you don't have them and double click on Content.json to assign them.
Yesterday at the xamarin webinar I asked if it was possible to install xamarin studio for IOS development on a windows machine and was given the answer that it was possible but developers usually went for visual studio. Today I've tried to find info about how to do this but can only find posts that it can only be done via Visual Studio. Most of the posts are a couple of months old though so which is the correct answer?
Unfortunately, I think your fears are true. Another post talks a little about this:
How to develop iOS app using Xamarin Studio on Windows?
The official Xamarin documentation also says pretty clearly that you need Visual Studio to do iOS development in Windows. On top of that, you also need a Mac on the network to compile the iOS project.
Using Mac build Host you can do but you'll need the networked mac
for developing and debugging too.
or else you can use Xamarin Live Player using which you can
debug,develop and deploy the app completely in windows without the
help of any Apple system but to sign and release the app to appstore
you will need Apple System though
You can access Xamarin Studio from a Windows machine by accessing a remote Mac from services such as MacinCloud.com. Although you are not running Xamarin Studio directly on your Windows machine, the ability to access a Mac server for development allows you to run Xamarin Studio, and other Mac-only tools easily.
I was trying some code for push notification(which has sender windows phone client and wcf service) in windows phone 7.0.
I then install windows phone 7.1 beta update
and run the same code
but i m getting
"Connection failed because of invalid command-line arguments."
error.
I want to know how to solve this issue......
It seems like you have either have a misconfigured project or a failed installation of the updated SDK.
Your first choice would be creating a new WP7 application that targets 7.0 systems (if still needed). See if you can launch it through the emulator (which I am assuming is the issue). Try reloading the same project again.
In the most extreme case, remove everything WP7 dev-related and re-install the dev tools.