Is there a way to target Xbox device family specifically when creating a new UWP application? Thus making that application package unavailable for the other platforms, while potentially have a different package for other platforms?
Currently I'm trying to create a package for Xbox only by adding
<TargetDeviceFamily Name="Windows.Xbox" MinVersion="10.0.14000.0" MaxVersionTested="10.0.14000.0" />
to the package.appxmanifest. Unfortunately this gives permission error on uploading via the dev center:
Package acceptance validation error: The package *.appx targets the following Windows 10 device families for which you don't have permission(s): Windows.Xbox
I think this is the correct way to do it and that the permissions might be granted somewhen after the anniversary update? When will publishing be possible? Or is there another program you have to sign up to for being allowed to publish an Xbox only application / get the required permission?
Currently, Windows Store is not ready to accept XBOX app. As pnp0a03 mentioned, Microsoft will publish the new Dev Center feature and publish more details about publishing XBOX target app in Store, maybe later this month
Setting TargetDeviceFamily dependency is the right direction, the current available device families are Windows.Universal, Windows.Mobile, Windows.Desktop. Please waiting for the updates from Windows Store side.
Related
I'm iterating on an app and have deployed/redeployed via Visual Studio, in addition to playing around with an appxbundle of the app. Somehow I've gotten into a state where my app does not show up in the user interface, however the app still shows as installed in the device portal.
When I attempt to uninstall via the app portal, I am confronted with a rather generic error "Failed to uninstall package ". I cannot deploy/debug via Visual Studio. When I attempt to deploy/debug via VS, I get an error "RemoteCommandException: Another user has already installed a packaged version of this app. An unpackaged version cannot replace this.".
My question is, is there a way to "force" uninstall, or another method to clean up the uninstall, or discover the reason the app uninstall fails via the device portal? I don't want to wipe the device if it's possible to avoid.
Are you sharing the HoloLens with multiple people, so have multiple accounts in it? When they use their own Azure Active Directory (Azure AD) accounts, multiple users can each keep their own user settings and user data on the device.
And according to the error message you got, this issue happens because the other user installed the same package in your HoloLens, you need to log in as the user who did it and uninstall it from that context. If you don’t know how to check the list of the users signed in your device, please go to Settings > Accounts > Other users, more information please see:Share your HoloLens with multiple people
Full problem text:
Package Microsoft.ApplicationInsights.Web 2.4.0 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1)
Package Microsoft.ApplicationInsights.Web 2.4.0 supports:
- net40 (.NETFramework,Version=v4.0)
- net45 (.NETFramework,Version=v4.5)
So when I try to access Live Metrics Stream in Azure I get the message:
Not available: your app is offline or using an older SDK
and the following step-by-step guide to getting it:
Make a copy of ApplicationInsights.config if you customized ApplicationInsights.config.
In Solution Explorer, right-click your project and choose Manage NuGet packages.
Select Browse.
Search for Microsoft.ApplicationInsights.Web, select it and choose Install/Update. You need version 2.2.0 (or later).
Reinstate any customizations you made to ApplicationInsights.config. Most of the changes you'll see when you compare the files are because we removed some modules and made others parameterizable.
Rebuild your solution.
(I haven't customized no ApplicationInsights.config so started at 2, got the error after 4)
So I'm not entirely sure what the problem here is, on thing I guess from the problem text is that ApplicationInsights.Web works with .NETFramework and not with .NETCoreApp. In that case my question would be:
What's the ApplicationInsights.Web alternative for .NETCoreApp? Plus, why does Azure recommend this step-by-step guide to me? Can't they see that I'm running a .NETCoreApp?
In case it's relevant:
I have student access to Visual Studio and Azure through something called Microsoft Imagine.
The guide is for classic MVC, not MVC Core.
For ASP.NET Core, you should be able to add App Insights with the connected service in Visual Studio: https://ppolyzos.com/2017/03/07/add-application-insights-in-a-net-core-app-using-vs-2017-and-connected-services/
To add one of the supported connected services you can right-click on
your Project and select Add Connected Service. Select Application
Insights and, from the next dialog, click on the Start Free button to
start the registration of Application Insights in your app.
Then, connect your Microsoft Azure account, choose your subscription
and resource group and, at the bottom, select whether you want app
insights to continue collecting data beyond 1 GB/month or not, and
click on Register. A popup will appear displaying the progress of App
Insights registration process.
Also, the package that the connected service installs is: https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore/
I am trying to transfer an app of mine into my company iTunesConnect account but are getting the error:
You can't transfer this app because of the following reasons:
Sandboxed Group Container
You can only transfer sandboxed apps that are not sharing a group container.
the thing is, my app isn't using the group container any more, it was in an older version but not the currently shipping version in the Mac App Store.
does anyone have any experience with how to go about transferring the app?
Even though my app wasn't currently using a group container (it had in the past) I couldn't transfer it. I had to re-upload as a new app losing all my reviews.. :(
It appears to be impossible. I got the following response from iTunes Connect Support (September 15, 2017):
I have reviewed your enquiry and found that once the app has the
entitlement included, an app transfer will not be possible, even if
you submit a new version without the entitlement. However, you can
transfer the app via the binary reassigned process.
By completing this process (a "binary transfer"), the app will effectively be a new and separate app on the Mac App Store. This might of course be very inconvenient, but there's not really anything to do about it, unless Apple changes the rules.
This just started happening today after I got a message from xcode to agree to new t&c's.
I can't put anything on the device, on any of my computers.
Doesn't work on my macbook, doesn't work on my mac mini, doens't work with existing projects that worked fine until yesterday, doesn't even work with completely new projects.
I constantly get the message:
writeDictToFile:1241 open failed for
/Users/georgecook/Desktop/test/iOS/obj/iPhone/Debug/mtouch-cache/install-shadow-directory/339bee33bc83c8e05fbd004dcc732c0b/20715d40747e047ba8a4ce4c1d2672ef90161df5/ManifestCache.plist
: No such file or directory MDMCacheDirectoryManifest:1315
writeDictToFile failed to write to
/Users/georgecook/Desktop/test/iOS/obj/iPhone/Debug/mtouch-cache/install-shadow-directory/339bee33bc83c8e05fbd004dcc732c0b/20715d40747e047ba8a4ce4c1d2672ef90161df5/ManifestCache.plist
: No such file or directory error MT1006: Could not install the
application
'/Users/georgecook/Desktop/test/iOS/bin/iPhone/Debug/test.iOS.app' on
the device Gandalf the white: Your application failed code-signing
checks. Check your certificates, provisioning profiles, and bundle
ids. Probably your device is not part of the selected provisioning
profile (error: 0xe8008015).
No idea why this is suddenly happening - this is really not good - how to resolve this?
I tripped over this one recently too.
The key is this part of the message:
Your application failed code-signing checks. Check your certificates, provisioning profiles, and bundle ids. Probably your device is not part of the selected provisioning profile
Likely, your provisioning profile has expired. The easiest way to solve this is to launch Xcode, create an empty project, and hit Run. This will go over a series of dialog boxes offering you to fix your provisioning profile until it deploys. Once this happens, you can switch back to Visual Studio/Xamarin Studio and deploy.
One reason this can happen is if you have multiple developer accounts set up in XCode. Here are the steps
Verify that your device is on Apple member center
Verify that your device is part of the relevant provisioning profile
Repeat steps 1 and 2 for each account
Create a new project in XCode and run it on the device. XCode may ask you to select the team (if you have multiple accounts)
If you have multiple developer accounts (teams) set up in XCode, the repeat step 4 each time with a new project and select a different team each time.
These steps ensure that XCode clears the way for Xamarin. The idea is that Xamarin does not allow you to decide which "team" to use, so you want to make sure that XCode has done the setup for EVERY team.
I just had this ManifestCache.plist : No such file or directory problem. I checked device logs (View -> Pads -> iOS Device Log) to see why it was happening. Logs said it was rejecting an upgrade. Upgrade, I thought to myself, that doesn't sound right...then I remembered I had an app on my iPhone with the same identifier to.dima.application from a previous version which I forgot to uninstall. Removing the old app cleared up this issue for me. Hope this helps anyone else who has the same problem! :)
It works! I have found the solution.I was facing the same problem. Somehow there was a misconfiguration in Xamarin. The entitlements.plist had a wrong manuel entry. The cert ist checking all the values in it and if you have a manuel entry there it is not working anymore. Apple is searching somehow only for own entry they are needing.
I spent sometime on developer portal to find out the problem, it occurs because of distribution APNS or development. It did not fixed, after restoring all provisioning profiles and certificates, . In my case solution was letting Xamarin choose signing profiles. I did not use info.plist auto signing which did not solve either but changing Project -> iOS Bundle Signing -> Signing identity, Provisioning Profile Auto solved all issues for development and production cases.
I had the same issue, and so I opened Xcode and updated all my profiles, but nothing happened. So I added the device UDID in the developer portal to the team I was developing for, went to Xcode and updated the profiles again, and then it worked. Don't know if the device must be registered to be able to build to device or this triggered some other update to my profiles that suddenly made it work.
Today they published a new revision of the Apple Developer Licence agreement.
The error message was essentially the same as OP's. The true reason only became apparent when creating a new project in XCode on the Mac, where more useful warnings show up in the "Deployment info" section of the "General" tab.
I had to log in to apple.developer.com, there was a red panel asking me to accept the new licence conditions, and as soon as I did that, deploying apps from Xamarin immediately worked again.
Is there any way I can distribute a "privileged" app prior to marketplace approval?
It's kinda hassle for me to "push" app to the device using Firefox OS Simulator every time I need to test it. Would it be great if I can just point my browser to app's html file and then it will automatically re-install the app? Just like what android *.apk does.
You cannot install a privileged app on a real device without the simulator dashboard (or app manager) if you didn't submit it to the marketplace first (and was approved). For security reasons, the application needs to be signed, so it's why you need to publish it to the marketplace.