I am developing a windows 10 universal app. There are no build errors in the app. When I am trying to debug, the following error occurred.
Severity Code Description Project File Line
Error Error : DEP0800 : The required framework "C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.Midi.GmDls\10.0.10240.0\.\Appx\Neutral\MidiVoices.appx" failed to install.
error 0x800B010A: The root certificate and all intermediate certificates of the signature in the app package or bundle must be trusted.
Why this error occured and how can I resolve this?
Just as #Hans Passant mentioned, this is a known issue.
It is because the MidiVoice.appx is not properly signed in current version of SDK. This issue has been fixed in TH2 SDK. So you will be able to make it work when TH2 SDK update available to you.
[Update]
Visual Studio update 1 included the TH2 SDK update. The issue has been resolved.
Mild correction -- the update 1 doesn't seem to have the right version. You need the "10586" SDK, not the "10240" version. I downloaded tools for universal windows app and then hand-selected the latest SDK.
After the project had to be hand-edited to bump up the min version (installing the 586 SDK will unintall the 10240 SDK) and reload. There's a scary "reinstall missing features" that actually doesn't seem to do anything, and the DLS reference needs to be removed and re-added.
Related
I have a UWP app (from a Xamarin.Forms app) which debugs fine on the computer. But when I try to debug on a phone, I get the following error:
Unable to debug Windows Store app '....exe'. The debugger was unable
to find the registration for the target application. If the problem
persists, try uninstalling and then reinstalling this application.
The app does get installed on the phone and can be executed there. But I can't debug it with Visual Studio.
Meanwhile, the error I see in the error list in VS is:
DEP6700: LaunchMsvsmon failed on the device side. [0x800401F3] Invalid
class string (Exception from HRESULT: 0x800401F3 (CO_E_CLASSSTRING))
I uninstalled both on the computer and on the phone, I rebooted both, I deleted the .vs folder, bin and obj folders... Nothing helped.
What are these errors telling me?
Currently, the Maximum SDK version supported by windows phone is Windows 10 Creators Update (Build 15063). If your project target version is Fall Creators Update (Build 16299), it will not be supported.
If your Shared project is Portable Class Library, you could modify the target version to Windows 10 Creators Update (Build 15063).
However, if you have used .NET Standard shared project, and it only support Fall Creators Update (Build 16299). You could not modify the target version.
I've created a pretty simple app that uses banner ads.
App works great with debuging mode with ads test ads showing up. But when I'm creating a appxupload and uploading it to store I'm getting error.
Your package Microsoft.Advertising.Xaml specifies version 10.1707.2.0, but 10.0.0.0 is the minimum available version.
What exactly is the problem, why package is getting rejected and how can it be resolved?
According to the description of the error, you have installed Microsoft.Advertising.Xaml package which can't work on the Windows version below 10.1707.2.0 (which hasn't even been released to the general public). Your app declares that it can work on every version of Windows 10. This is in a collision.
Had the EXACT same problem. Finally got mine to work by uninstalling the MSI from https://marketplace.visualstudio.com/items?itemName=AdMediator.MicrosoftAdvertisingSDK and installing the Microsoft.Advertising.XAML from NUGET package manager. It was only 1 version earlier, but let me publish my app to the store.
I have a problem with Visual Studio Community 2015 and Xamarin.
When I want to debug my Program the virtual device start but the App does not open.
This is the Log:
1>"aapt.exe" exited with code -1073741819.
1>The file "obj\Debug\android\bin\packaged_resources" does not exist.
I don´t know how to fix this problem, I hope you can help me.
Complete Log: Here
This is a known issue currently, where a too new version of Android SDK Build-tools. This error will occur when version 24.x is used, due to Xamarin being compatible with 23.x
We have a technical bulletin available on our release blog, which describes the issue and the solution:
Recommended fix: Uninstall Android SDK Build-tools version 24 using
the Android SDK Manager.
Another separate issue is that version 24 of the Android SDK
Build-tools package requires Java JDK 1.8 or higher. This can cause at
least 1 error:
“java.lang.UnsupportedClassVersionError: com/android/dx/command/Main :
Unsupported major.minor version 52.0”
Source: https://releases.xamarin.com/technical-bulletin-android-sdk-build-tools-24/
Thanks!
Here are a few solutions that worked for some users, as this error might have multiple causes :
Check your AndroidManifest.xml file for any typo. File names must not contain characters like -. This is also the case for any code file. Oh, and by the way, don't use keywords as file names. For example, a file named New.cs might break your app.
Check that the Android SDK you're targeting is installed on your computer. Click Tools->Android->Package manager and install or update the SDK you're targeting. Also, install tools, build tools and platform tools. You might want Android Support Library and Google Play Services too.
According to the logs you put on pastebin, it seems like the last thing done before the build fail is to check for Android SDK Build tools rev 24. There is high chances you lack those files, or that some are corrupted. I'd delete and reinstall everything.
I've developed an simple and small Universal Windows App that uses EF7 and SQLite. The app builds normally and it runs perfectly from Visual Studio. I also can run it directly from Windows 10 in the start menu after the I side loaded it (once the app package is generated).
My problem is that I can't test the app after it's package is generated because of an error on appcert.exe.
If I generate app package to x86 when launching windows app certification from visual studio right after the package is generated I get the error "the appxbundle could not be implanted" even before the test starts.
If I generate app package to x64 when launching windows app certification from visual studio right after the package is generated the test starts normally but before it's done I get the following error: "an unhandled microsoft .netframework exception occurred in appcertui.exe".
The appcert.exe crashes and does not tell me why.
I've searched in google and I've looked at windows log event but found nothing helpful.
I just don't know what to do. My app is finished, I can generate it´s package but I can´t generate the ".appxupload" because of this error I mentioned.
Can someone help me?
The file C:\Program Files (x86)\Windows Kits\10\App Certification Kit\binaryinfo.dll is CLSID {3866CD68-0FC3-4563-8888-E107295BC485} on my machine.
I was able to reproduce your crash by unregistering binaryinfo.dll on my machine and clicking "Validate Store App".
Maybe a fix for your issue to do register this dll (maybe all of them?).
From an administrator/elevated command prompt
regsvr32 "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\binaryinfo.dll"
How your machine got into this state...unknown.
I've made a fresh install of Windows 10 and its SDK in a virtual machine on Virtual Box. The appcertui.exe is running fine and my app was tested successfully.
It might be a problem in the installation of the .NET Framework since I updated from Windows 7 to Windows 10.
I will try to completely reinstall both .NET Framework and the SDK to solve this issue. If none of this works I will reinstall Windows 10 from scratch on my computer.
I need this for the build server - I'd like to avoid installing full Visual Studio there.
I use the newest v12 MSBuild to build the solution with the app. Installing .NET Framework 4.5.1 and Windows 8.1 SDK got me through several compilation errors. With all that installed, right now, I get this:
error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\WindowsXaml\v12.0\Microsoft.Windows.UI.Xaml.CSharp.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
The targets file is present on my development machine with Visual Studio 2013 installed, so I guess it got there with VS 2013. When I tried to paste the whole folder to the build machine (I know, a stupid thing to do), I got the following compilation warnings and errors:
warning MSB3644: The reference assemblies for framework
".NETCore,Version=v4.5.1" were not found. To resolve this, install the
SDK or Targeting Pack for this framework version or retarget your
application to a version of the framework for which you have the SDK
or Targeting Pack installed.
XamlCompiler error WMC1006: Cannot
resolve Assembly or Windows Metadata file 'System.Runtime.dll'
Xaml Internal Error error WMC9999: Type universe cannot resolve assembly:
System.Runtime, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a.
Obviously, copying and pasting stuff around is not a way to go. Is there some proper approach to achieve what I want?
EDIT: The build machine has Windows Server 2012 installed, not Windows 8.1. Could that be a problem?
EDIT 2: After comparing outputs of msbuilds executed both on development machine and build server, I've noticed that the folder C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETCore\v4.5.1 is missing from the build machine (there is only 4.5 folder). After pasting it, I got the following error:
CompileXaml error WMC9998: XBF generation failure due to missing
Windows 8.1 Support, Set property
<DisableXbfGeneration>true</DisableXbfGeneration> in your Project file
and try again.
There is still something missing from the Windows 8.1 toolchain...
Since it's a windows store app, and Windows Server 2012 doesn't have an app store, I'd say the libraries needed in order to compile the app are just missing from the OS itself. I suggest running tracer on a windows 8.1 box to see what files are accessed during compilation, and copy them to the server. I'm not certain that this will work, but it's the likeliest scenario I can think of. You can use something like Process Monitor for this
See what files/registry keys are being accessed by application in Windows
Alternatively, you might want to monitor the temporary build folder in .net to see what assemblies get copied locally during the build.
EDIT: Microsoft doesn't officially support this http://msdn.microsoft.com/en-us/library/windows/apps/br211384.aspx
Did you download and install Microsoft Build Tools 2013 on the build server? The v12 version of MsBuild is now released as part of Visual Studio (instead of the Microsoft.NET Framework) and you'd want to use this separate install to get the MsBuild v12 bits on your build server.
I just did this a few weeks ago for a Windows 8 store app so it should be the same for Windows 8.1. As long as the build machine is running Windows 8.1, All you should need to do is install the latest Visual Studio Express for Windows Store Apps on the build machine and you should be fine. It should install everything you need.