I'm trying to write an app in Xamarin for my company. The SDK manager keeps failing to install everything, seen in this screencap of results.
"Operation failed: Downloading Android Emulator - "The decryption
operation failed, see inner exception.""
Has anyone else had this problem and worked it out? Or at the least how can I look up this inner exception for more info? Any help is appreciated, I've been stuck on this for days. I'm still very new to programming so please explain things to me like I'm 9, thanks.
Edit: I can't really provide more details because I haven't done anything so far. I try to follow this tutorial but when I open the SDK manager, it asks me to Repair, which fails with the messages in the screencap. My project is still basically blank at this point. What few forum posts I can find that are at all relevant refer to a different problem that happens to have the same error message.
I've tried starting over on another computer. No dice.
The suggestions still didn't help, but I managed to configure and connect my phone and am using it as a test platform rather than the emulator. Takes longer, but at least it works.
Related
I am currently working with MediaFrameSourceGroup and I have noticed two things today where I do not know how to fix them. I hope someone can help me or at least explain them to me.
while I am searching with await MediaFrameSourceGroup.FindAllAsync() for all possible MediaFrameSourceGroups I wanted to get DisplayName and other parameters. This works for all parameters except the Id.
As soon as I try to access it, my debugger detaches itself with the code 'The program 'Unity' has exited with code 1 (0x1).'.
Although I have activated the research mode and was able to see both depth sensor with the SensorVisualization Sample, the depth sensor is not listed.
Now I have a more general question/problem, which I would like to mention here to not open a new question. I hope this is ok.
When I have loaded the app on the HoloLens 2 and connected the debugger, I get the following error
System.DllNotFoundException: Unable to load DLL 'advapi32.dll': The specified module could not be found. This is accessed in WindowsMixedRealityDeviceManager.cs
According to similar questions I found with Google, the problem should not occur in the Unity version (2018.4.22f1) I use. How can you fix such an error without ideally updating Unity. I must honestly admit that I'm afraid of updating Unity, because I think that after that the app won't work anymore or I'll get other errors on board.
while I am searching with await MediaFrameSourceGroup.FindAllAsync() for all possible MediaFrameSourceGroups I wanted to get DisplayName and other parameters. This works for all parameters except the Id. As soon as I try to access it, my debugger detaches itself with the code 'The program 'Unity' has exited with code 1 (0x1).'.
Where is the error message you got? In Unity Editor or Visual Studio? It seems like Unity crashed when you're debugging the app. Would you be able to copy a stack at the crash? Thanks.
Although I have activated the research mode and was able to see both depth sensor with the SensorVisualization Sample, the depth sensor is not listed.
Just as the link referred to in your comment says, currently, the research mode API only supported invoking directly from C++. However, it should be possible to use the API from C# as well, but you would have to rebuild the entire set of convenience functions / wrappers in the HoloLensForCV project yourself.
When I have loaded the app on the HoloLens 2 and connected the debugger, I get the following error System.DllNotFoundException: Unable to load DLL 'advapi32.dll': The specified module could not be found. This is accessed in WindowsMixedRealityDeviceManager.cs
It should be a Unity side issue, we recommend that you re-open the bug or submit a new feedback to the Unity product team. Besides, we always recommend the latest Unity LTS (Long Term Support) stream as the best version so that we can avoid some known issue, and the current recommendation is to use Unity 2019.4.11f1: https://unity3d.com/unity/qa/lts-releases
My Xamarin (PCL) Android application suddenly randomly crashes when it released. It sometimes happens even when you are not currently using it and then message that app stopped working appears.
I wonder, is there any way to track whats going on, maybe there are some logs which I could have a look, or anything else to find out what the issue as I said it randomly happens and hard to find the problem.
Many thanks in advance.
A fast solution would be to plug your device and use the Android Device Monitor to see if it print out something on the device logs. A more reliable solution would be of course to integrate a crash reporter system like what the others have suggested or Crashlytics.
You might need to add a crash reporting tool like HockeyApp or VS App Center, or wire up your own global exception handler
I am trying to setup a development environment in Visual Studio Community for development with Xamarin.Forms. In order to make sure the Android Emulator was working, I followed the QuickStart Xamarin.Android tutorial found here.
When I Start Debugging with any number of Virtual Devices the output is always the same; the application does not show up, but the AVD successfully starts up and I can also successfully interact with OS; when trying the close the AVD (with the x icon on the top right) a pop-up dialog appears saying "There were Deployment Errors. Do you wish to continue? Yes\No". The frustrating part is that no matter my response there is absolutely no useful error informations, or warnings or messages for that matter. You may think this is a duplicate question but it is not. I have had problems with a similar problem in which the fix was to downgrade my Android SDK BuildTools to a version lower than 24.0. The was to circumvent an upstream bug that provided the error message: java.lang.UnsupportedClassVersionError blah blah blah. The problem here is I get NO error and my highest version Build Tools are version 23.0.3 which should be fine. Here is a pic on start-up:
AVD
Unfortunately as I am only a begginer user I am not permitted to post more links and images. Apologies for the images as links I am still only permitted to post images in this way.
Thank you for taking the time to help me out.
Hi anyone with a similar problem, this is what worked for me in this particular case. I started the AVD before starting Debugging, the application then showed up in the emulators device menu and everthing is working. I have been stuck with this problem for Five whole day trying dozens of things. Pheeeeuuuuuuw!
I am at a complete loss with this. The articles at msdn either seem to be useless or I'm simply missing some major points.
I have an app which I've released on the store, a simple soundboard. Over the past few days I've had a LOT of crash reports come through which I'd of course like to fix if possible.
I've downloaded the xslx spreadsheet and one of the cab files located in it. I open it in visual studio and get as far as the first picture on: http://blogs.msdn.com/b/uk_faculty_connection/archive/2014/09/01/debugging-crashes-of-your-apps-and-games-on-windows-phone-8.aspx
The symbols seem to be where im running to problems I guess. The instructions seem about as clear as mud.
I follow the link to http://msdn.microsoft.com/en-us/library/windows/hardware/ff557573(v=vs.85).aspx to download sybols. It states: "Run the provided symbols installers from the WDK download on the Windows Connect site"the page doesnt mention anything about symbols. I've read a ton of articles and none really explain any way of doing thing.
I've tried playing around and see if I can figure it out but all I ever seem to get is KERNALBASE.dll not found and no matching binary found.
If anyone can point me in the right direction on how to get anywhere at all with this I'd be greatly appreciative.
the app was written in visual studio express 2012 in C#
I want to publish our iOS application to iTunes using Xcode but I get the following errors.
Your application contains non-public API usage. Please review the errors, correct them, and resubmit your application.
The app references non-public symbols in Payload/XXXXXX.app/XXXXXX: NSZombieEnabled if you think this message was sent in error and that you have only used Apple-published APIs in accordance with the guidelines, send the app's nine-digit Apple ID, along with detailed information about why you believe the above APIs were incorrectly flagged, to appreview#apple.cpm. For further information, visit the Technical Support Information page at http://developer.apple.com/support/technical.
We use Xamarin studio to code the application, before this we published our application many times without any error, but we cant update it to new version, and in this new version we only changed some fonts and colors and I think this errors are not correct.
I know that there is some same problems for others and I read all this questions and asnwers but I cant fix the issue.
I enabled NSZombie in the settings but nothing changed.
Please let me know if you need more informations to help me solve this issue.
Regards.
You're trying to publish a debug build.
Uncheck "Enable debugging" in the project's iOS Build options.
Turn off zombies, and search for underscores in your code (its going to be a pain) to find uses of private API. If it doesn't work, contact apple.