I am designing a simple webBrowser with webview, in VS 2010, when I compile program, it's okay, and even when I run it in emulator it works all right and I see the window and button, but when I install on device, immediately says 'stopped' and closes the application without showing anything.
I use API 8 to compile and install unsigned version and try to install it on android 4 or higher.
Appendix: When I run project in xamarin, it doesn't create apk file, nevertheless I did all configuration said in docummention.
What should I do to run on device or when can I compile it for once?
Related
My unity project includes an unmanaged dll that links to portaudio dll which I've built, everything is configured and built for x86_x64 architecture. My unmanaged dll uses portaudio to open an ASIO audio stream.
I want to build it as Universal Windows Build.
The problem is: a standalone build of unity project works properly on windows 10, also Unity editor works fine, but when I build a Universal Windows Build I get a working application but without sound at all. Logs show that portaudio opens stream successfully and gets all properties of the ASIO driver, which in my case is ASIO4ALL, however when I call PaAsio_ShowControlPanel() it opens ASIO4ALL's settings window, but shows that it sees no hardware devices at all, as opposed to listing them when running the same method in a standalone build.
I tried enabling mic permission in unity, visual studio and windows settings.
I also tried running everything as admin, did not work.
Debug output I got when building the generated visual studio 2019 solution included those lines:
Exception thrown at 0x00007FFDD17BD759 (KernelBase.dll) in MyApp.exe WinRT originate error - 0x80004005 'The window has already been destroyed.'.
onecoreuapdriversmobilepcsensorsconvergenceapiwinrtpublicinternalsensorserver.cpp(74)Windows.Devices.Sensors.dll!00007FFD7C3A2E23 (caller 00007FFD7C3EDA61) ReturnHr(3) tid(4a70) 80070490 Element not found.
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 have an application that i want publish it using application packages file and install manually i don`t want to use Microsoft Store for publishing my app. I create my application package files as you can see below
After that when I want to install my application package from Windows 10 iot Device Portal I didn`t got any error but when application run it stucks on splash screen page.
Generally, if you encountered an app hung up when running, you can follow the below steps to troubleshoot.
Try to deploy/debug the app from Visual Studio;
Try to deploy/debug with a blank app;
Set break points or trace the event log to check if there is some exception or what code causes the hung up.
When debugging with Visual Studio, checked the Compile with .Net Native tool chain in Debug setting, by default, when the app runs in debug mode, it will not use Compile with .Net Native tool chain. Please see this blog.
If possible, you can share the code of your splash page.
I have created a windows application using c# VS express 2012. The app works great in the VS environment. I have published the application using VS(ClickOnce) to the Desktop as an offline application, which does not check for updates. The app is not signed and security is disabled. The application seems to install fine when I run the setup.exe file. However, when I try to run the program from the start menu nothing happens. In the task manager, a process for the application appears for a few seconds then just goes away. The app window doesn't show and there aren't any indications of an error. If I navigate directly to the .exe of the app (%userprofile%\appdata\local\apps\2.0\%random id%......) and run it that way, it starts up and appears to function as designed. I've done some research and found that certain drivers and software (if installed) will cause this behavior (i.e. Kensington Mouse driver and Provencia software(?)). I've checked and I do not have either of these installed. Any help with this will be much appreciated.
Thanks in advance.
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