I've got a BackgroundTask which should be Extended with the ability to Play Music. Therefore, i Need to include this capability into the Package.appxmanifest-file. As soon as i include the capability
<uap3:Capability Name="backgroundMediaPlayback"/>
in the Package-Capabilities-section i get a Validation error stating the my app manifest must be valid as per scheme. If i remove the line above, everything works fine. My package node is as follows:
<Package xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:mp="http://schemas.microsoft.com/appx/2014/phone/manifest" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" xmlns:iot="http://schemas.microsoft.com/appx/manifest/iot/windows10" xmlns:uap3="http://schemas.microsoft.com/appx/manifest/uap/windows10/3" IgnorableNamespaces="uap mp iot uap3">
I searched the web and found out that this could be a bug in Visual Studio, but it should be fixed from Version 15.2 on(https://developercommunity.visualstudio.com/content/problem/44306/package-an-uwp-project-with-capability-of-backgrou.html).
Nevertheless, i am not able to compile the app including above capability. I did also a repair of my VS2017 Installation, but it did not help. The app is targetting the Windows 10 fall creators update (10.0; build 16299) for both, min and max Version. It is designed to run on a raspberry pi.
Do you have some clues?
EDIT: The BackgroundTask has been created using the downloaded template from https://marketplace.visualstudio.com/items?itemName=MicrosoftIoT.WindowsIoTCoreProjectTemplatesforVS15
Referring to this post
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/8efde534-f84a-48d7-9dd5-fec5043a894c/uwphow-to-use-a-restricted-capability-?forum=wpdevelop
it seems it is necessary to Keep a certain order. However, moving the uap3-Capability before the DeviceCapability solved my Problem. Strange, isnt it?
Related
I have been dealing with the same issue for a few days now. I'm unable to upload any app store connect files due to the libAgoraRTMWrapper file. To be clear, this entire app has been built through Unity using agora SDK. The reason for failure, according to XCode, is that the wrapper "doesn't have the correct file type for this location". Invalid Swift support.
This leads me to wonder if the libagoraRTMWrapper is even necessary. Yes, I would like to keep using RTM but not at the expense of several build failures.
As a sidenote, XCode does mention that the build is being made for iOS but the wrapper was built for iOS + iOS simulator. I don't remember ever specifying that but it could just be the way the SDK was initially imported.
this library is necessary for RTM to work. Do you have a custom build setting for the project? It is verified that the included SDK Demo works on iOS builds. Perhaps you can build that and compare the build setting to yours to find out what went wrong?
I have an app I have been working on that was running fine.
I upgraded to the latest Xamarin with mac support and now I get an error when I try to use HttpUtility.ParseQueryString.
I have an App.config file and it is telling me that it can't parse it, but this happens when trying to call ParseQueryString. How are those 2 related?
I thought I had found the problem because my app also has a ServiceReferences.ClientConfig file for http client settings. I copied my App.config section to the ServiceReferences.ClientConfig file and that fixed it until I went to show my fellow dev the new error.
The new error was saying something about Path.Combine path1 being null.
I looked up that error and found a reference to a page talking about MacSupport in xamarin here: https://searchcode.com/codesearch/view/8556026/
I don't know if they are related, but that is the closest I found to the stack trace I was seeing.
Can anyone tell me what changed in Mono 4.8 for Mac in Xamarin that would cause an issue with HttpUtility.ParseQueryString and how to solve it?
System.Configuration is a common point of pain during mono upgrades, as it's behavior sometimes subtly (or not so subtly) changes.
You'll need to post a much larger chunk of information here for anyone to be able to help you.
Or you could post on the XM Forms or file a bug if you believe this is a bug, as those are a more appropriate place for such reports.
I have a solution with 4 projects 2 PCL's, a Droid Library and a droid App. When I reference the Droid Library from my Droid Application at compile I'm getting:
Error XA5211: Embedded wear app package name differs from handheld app package name.
In both Xamarin Studio and Visual Studio.
Thing is it's not a wear app package nor do I have a handheld app package. Im just trying to reference a Library I created from an android App I created. I cant find any settings in either the csproj file the sln or the IDE that have changed that made my driod library into a wearable library (Im sure I changed something just dont know what) Its here somewhere just no idea were or what I'm looking for besides scanning for the word wear which doesn't seem to show up anywhere. I looked back through my change history and I dont see where it got messed up at.
Until last week everything was fine. Then I started trying to get the latest release of Xamarin.Forms to allow my code to compile. I changed a number of settings over a week of debugging that issue and finally got everything to work again by setting my target Platform to 6.0 and downloading the latest Android SDK.
The Libraries I'm attempting to reference that cause the issue I have on GitHub # https://github.com/Indiponics/IndiXam-Lib in case anyone cares to look at the csproj file etc.
The solution is easy. Open the .csproj file of your Android app and find the project reference you need to work. It might look like this:
<ProjectReference Include="..\MyWearApp\MyWearApp.csproj">
<Project>{D80E1FEF-653B-448C-B2AA-609C74E88340}</Project>
<Name>MyWearApp</Name>
<IsAppExtension>True</IsAppExtension>
</ProjectReference>
The problem is with the extension part. Simply remove the IsAppExtension line and any other than Project and Name. It should work now.
I think we lost an entire man-week on this issue!
https://developer.xamarin.com/guides/android/wear/working-with/packaging/
I am not sure if this is a known bug or some conflict with jQuery Mobile within the Tool for Cordova project but when I use jQuery Mobile inside mine project the layout did not rendered correctly.
For example, start with a blank project. I then added both jQuery 2.1.3 and jQuery Mobile 1.4.5 from NuGet. Then inside the index.html, I have added a text input element. It is pretty simple and nothing is complicated. Then trying to run the project on both simulators and real devices would yield the result that the text input element did not appear at all, even though it resided inside the DOM. Further investigation provided the same result like this question: Tools for Apache Cordova: JQueryMobile wraps input tags inside a head tag?. This did not happened when I targeted the app with Android or iOS. Everything would rendered correctly in those two platforms.
I suspect that there are some conflicts when Visual Studio built the application and injected WinJS as well as jQuery Mobile. I have searched a lot of place and there are no mentions of incompatibility between them.
After trying everything, I gone back to the basic. I started installing Cordova CLI and tested to see if this problem would be there. To my surprise, the Windows 8.1 and WP 8.1 projects from the Cordova CLI build are working perfectly fine. Everything is rendered correctly, although there was an issue with jQuery Mobile changePage().
If this is actually a bug in pre-released software, then I hope in the final release, everything should work correctly. In the meantime, anyone would like to try suggesting me a workaround for this problem. I know there are at least me and the other guy from the question that I have linked above that had issue like this.
Thanks.
Update my finding: The problem is with the library winstore-jscompat.js. Apparently, even with the new CTP 3.1, the file is not the recent one from GitHub. I downloaded the new version from GitHub, replaced it with the old one, and everything works perfectly now.
The GitHub is from here: https://github.com/MSOpenTech/winstore-jscompat.
I'm not sure if this problem is connected specifically with log4net or this is some problem with VS.
Everytime I'm trying, I have the same result. But let's start from the beginning.
I'm creating a simply console application (.net 4) and using nuget to install the log4net library.
Now, when I want to add some code from it, intellisense works ok:
But when I try to compile it, I have an error
This is the only one assembly I found to this moment, I have this problem with. I have absolutly no idea what (and why) is going on. I have checked with two other solutions and problem is the same. I have not checked manually downloaded version yet.
Most likely there is an underlying dependency that is missing. One very common reason is the project is using the Client Profile instead of the full .NET 4.0. (Not sure about log4Net, but I run into this a lot when including third party libraries, esp. those with ties to the web). If I am correct, simply going into properties and changing the framework version to full .NET 4.0 will solve the issue.