I am getting the following error (see screenshot) after setting up my Azure Sphere and trying to run the Blink sample. Any ideas?Error
Did you put your Sphere device into prep-debug mode? This step installs a gdb debugger on the device and sets things up so you can sideload applications.
azsphere device prep-debug
I had an Object reference not found error while trying to build and cleaning component cache resolved the issue.
Also for VS 2017: folder was
%USERPROFILE%\Microsoft\VisualStudio\15.0_d9d88191\ComponentModelCache
When I'd that error (the same one), I had to clean the visual studio cache.
You can see at this web site. https://www.matteopozzani.com/visual-studio-cache-cleanup/
Related
I am trying to load the SDK for Vuzix through the SDK manager in Android Studio but for some reason it will not display the downloads in 'SDK platforms' and 'SDK tools'.
In the 'SDK update sites' tab next to the Vuzix link I added there is a red exclamation point that displays " cvc-elt.1.a cannot find the declaration of element 'sdk: sdk-addon' " when hovered over.
I am new to SDK's and have no idea what to do for this error. I've downloaded the android SDK's and sources for 26,25,24, and 23 thinking it could help but the error still shows up.
I still don't know what the error means but I solved it by connecting to my hotspot instead of my work network.
So my guess is it was a firewall issue or something, if anyone else has this error.
This means that the parser does not know the namespace. I tried it on Win7 and android studio 2.3.3 with the same result.
I tried it without the namespace or running android studio with oracle sdk. Both failed.
At the moment I try to run it on a virtual linux machine. Android Studio 2.3.3 will parse the addon xml file and download the files.
On Win7 I installed them manually, but they were not really integrated into to system and I stucked when I wanted to use the barcode SDK. maybe I am able some day to add simply this jar lib -
On a first look using linux seems to be the solution. But than I run into problems with the case sensitve file system. The vuzix SDK seems to need a linux system on a case insensitve file system.
*facepalm* and I am quite sure that i will fail at all. On linux a simple GUI compiles only against API 26 without errors.
I have VS 2015 Community with Xamarin, Android SDK, etc. installed and today I stumbled upon SyncFusions Controls for X.F that are free in the community license. I installed the SyncFusion Essentials Studio for Xamarin.Forms.
The problem is that I cant run the included Samples like SampleBrowser or ServerMonitor when I select Android or iOS. If I select UWP or WinPhone the apps run.
The issue is that the projects do not build. In The SampleBrowser for example I get 1400+ Errors when I want to build. VS recognizes almost nothing of the Code. But as I said everything that is not a Droid/iOS Project runs.
I have the Android SDK installed with API 19-23. AVDs are also configured. I also have a Macbook Air next to me that is connected to VS.
I tried cleaning the solution and re-building the solution without success. There were also no changes to the code made.
Edit: Here is a picture of the error list:
Edit 2: Here is the error list from "build only" on pastebin and as an image:
I found the solution. The comment to only show "build" errors lead to the errorlist you see in Edit2. There you see an OutOfMemory-Error. The resolution is the following.
I copy the solution in case the site will go down. Source: http://www.kiwipiet.com/2016/05/javalangoutofmemoryerror-consider.html
"I was getting a java.lang.OutOfMemoryError while trying to compile a Xamarin Android application after adding HockeyApp.
I found to ways to resolve this.
The first option is to add a Environment Variable called _JAVA_OPTIONS and set it to -Xmx1g. This sets the JVM heap size to 1GB. You can either do this from the commandline by calling
SET _JAVA_OPTIONS = -Xmx1g
Or you can edit your system environment variables:"
The “java.lang.OutOfMemoryError” error is a Xamarin issue and it occurs when the app size is exceeded some limit. You can refer the following bug report.
https://bugzilla.xamarin.com/show_bug.cgi?id=18327
Solution:
Right click the Android project and select Properties > Android Options > Advanced
Set the Java Heap size as 1G.
So I have setup my Xbox One as a dev device and actually was able to run my app on my Xbox, but in order to use some new APIs to turn off scaling and what not I had to change my app target version to Build 14332. Unfortunately, after doing this, I am now not able to publish or debug my app to my Xbox and I am not getting very helpful clues as to why not.
I even reverted the target version back to Build 10240 but I am still getting this error:
Severity Code Description Project File Line Suppression State
Error DEP0700 : Registration of the app failed. Deployment Register
operation with target volume C: on Package
MyCompany.MyApp_1.1.19.0_x64__5wbv4ypmprn7c from:
(AppxManifest.xml) failed with error 0x80070002. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app
deployment issues. (0x80073cf9) MyCompany.MyApp
EDIT: I found a work around. Restart my Xbox One. Literally, every time I run my app, I have to restart my Xbox One! :(
I came across the same issue, and while restarting the console didn't help me, I did find another workaround: go to Dev Home and clicked Remove all Visual Studio pairings. I was able to deploy right after doing that.
I've ran into the really similar problem, however with running on the remote machine. The solution was the same as Pedro Pombeiro did on his Xbox One. I opened Windows Settings > Update & Security > For developers and Unpair All. Problem was solved and I could deploy and run the app on remote PC.
It has been a while since I've published my app to Azure. During that time frame, I've upgraded my system from 32-bit to 64-bit meaning a fresh install of Windows and Visual Studio. And Visual Studio Update 3 came out and was applied. When I went to publish an update today, I received the following:
The following exception was thrown trying to publish: Root element is missing.
My web.config file looks fine so I don't think it's this issue.
The app works fine in debug mode so I don't think it's any of the .lsml files as is mentioned here.
And I tried this procedure to hand edit the .ls3proj file but it didn't seem to help.
I previously had an issue trying to publish when I upgraded from the standalone LightSwitch 2011 to Visual Studio 2012. I was able to overcome that issue using the method described in this thread.
Attempting to use this same method resulted in my new project has a full screen error saying "There are critical errors in the application definition metadata..." and 210 individual errors (max errors reached).
The first error, "Cannot create unknown type '{http://schemas.microsoft.com/LightSwitch/2010/xaml/model}GlobalAttributeGroup'." Doesn't make sense because that line in the .lsml is identical from the old project to the new project.
The second error, "Could not find any application definition in the project." Which I do not understand at all.
I am able to publish a simple "Hello, world" style app to my Azure account.
What could be causing this? How can I get more information about exactly which element is causing the issue? The log produced by running devenv /log was not helpful.
Matt Thalman was able to solve my problem over in the Microsoft Forums. The ServiceConfiguration.cscfg and ServiceDefinition.csdef were missing from the project when checked out of version control. Copying those over from a new project restored my ability to publish.
I am developing an iPad application with Xamarin.iOS and MVVMcross. So I have a PCL with my View-Model and my Model, and an iOS project with the view. I use Visual Studio.
Before, I used Xamarin.iOS 6.3.6 beta version, and when I tried to launch the app on the device, an .app file was created and getting it with my Ipad, I could launch the application (impossible to launch directly from Visual Studio).
Yesterday, I uploaded Xamarin.iOS to 6.4.1. On simulator, everything's okay. When I try to launch the application on device, now the app is directly installed but the build stop and the following error appear in the debug output :
Failed to load AOT module '<my PCL>' while running in aot-only mode: doesn't match assembly.
And if I click on my app icon on the device,a black screen appear and disappear immediately.
Does someone know why this error appear?
This looks like something was cached somewhere or not updated correctly.
Here are a few ideas to try:
Delete the app from the device.
Clean & Rebuild your app.
Build & install from Xamarin Studio on your Mac.
Copy the Debug configuration to a new configuration (DebugTest for instance), and run that configuration instead.
I regularly get the same issue here.
The workaround that I use is to switch the platform in the Visual Studio build Configuration Manager to "iPhoneSimulator", run a quick debug session on that, then switch the platform back to "iPhone", and the problem disappears for a while.
Unfortunately I have no intelligent reason as to why this works. It seems to be doing a better job of the "Clean and Rebuild".
After reading a similar bug, I found that clearing the mtbs folder on the OS X host which is located at $HOME/Library/Caches/Xamarin/mtbs/ fixes this problem for me.
I have to do it so frequently I just have a PuTTY session open on my Windows box to clear the folder. I do hope that Xamarin fixes this issue soon.
Make sure Linker Behaviour is set to Don't Link
Clean, rebuild, remove old version from app.
Worked for me at least.
This happened to me after I upgraded to XCode 5/iOS7. I noticed a warning that I hadn't installed XCode Command Line Tools. After I did that I rebuilt the application and it now runs.
I just had this problem and got it to work again by opening the Apple project properties and changing the provisioning profile identity from "Distribution" to "Developer".
My workaround on Mac is to
Close Solution in XS
Quit XS. Command-Q
Reopen it and reopen solution.
After that it usually works again.