I use Visual Studio Ultimate 2013 to build first Windows Phone 8.1 app.
After build, I get appxupload file and appx file.
And after that, I upload file to store, but I get Attention is can't test my app.
So, I use real phone to test with appxupload file and appx file, but 2 file can't install on phone.
And I build app again, I see "the option to create x86 package is disabled because it's not valid package that can be published to the windows phone store".
Do I miss something?
Why appxupload file and appx file can't install on phone?
How to build correct file upload to store?
Do I miss something? Why appxupload file and appx file can't install on phone?
For Windows Phone 8.1 app, you could deploy and test your app in Windows Phone Emulator first. While it would be highly recommended to test your app on actual device before you upload it to the Store.
For sideloading Windows Phone 8.1 app, you could try to use the Application Deployment tool:
• First you have generate your app package
• Then make sure the device is registered and connected
• Find the Application Deployment tool in Start menu
• Run the tool and browse the package file (.appx) then click deploy
For details, please refer to Deploy Windows Phone 8.1 apps with the Application Deployment tool.
How to build correct file upload to store?
To make your app pass the certification, you could re-create your app package following Create a Windows 8.1 app package.
After you finish generating package, please ensure your app pass the Windows App Certification Kit test first, which is not necessary but a best practice before submitting package to the Store.
It seems that your app fail to pass the certification for “the app must be testable”. You might as well add some notes for certification to the tester:
e.g. if your app requires users to sign in to a service, you need to provide a test account in it. This can ensure your app is tested correctly.
Related
I have a windows 10 uwp app that runs fine when i have it sideloaded in my computer or any users computer where they have full admin priviliges. i use appxbundle and click on install button to install the same. Even powershell installation works fine.
Some of our clients don't have access to C: drive and the installation of UWP app is incomplete or fails because they don't have any install permissions.
Is it possible to run UWP app stand alone or specify a different install location which is other than C drive where user has both read and write permissions .
I tried to use .exe generated in the bin folder of uwp x64/Release folder but that doesn't run as uwp doesn't support exe
Currently, there is no such feature in UWP. UWP can't change the install process when installing, which means UWP apps can't choose where apps should be installed.
But there is a setting for Windows 10 that could change the location where the UWP apps are installed.
You could go to the Settings app and navigate to System > Storage.
Under the More Storage Settings heading click on the link that says Change where new content is saved.
You can choose one drive from the drop-down menu under "New apps will save to" and then click Apply. A new folder called "WindowsApps" will be created in the drive you've chosen. And any new UWP app will be installed in this folder. Please note Windows 10 will only install new apps to the currently selected location. Existing apps do not get moved to the new location.
Like this:
I'm using the ide Visual studio 2019. I create a uwp app and i want to install the app to a computer without publishing it to the playstore.
I created a pfx file (certificate). Now i want to integrate the pfx file in the app manifest for deploying purposes. With Visual Studio 2019 i can only show the certificate and view the data.
But i didn't find a way to browse the own pfx file.
Now i want to integrate the pfx file in the app manifest for deploying purposes
You could create your app package sideload file using Visual Studio.
Steps for creating the sideload file: Solution Explorer-> Right-click the project ->choose Store->Create App Packages -> select I want to create packages for sideloading ->select Always for Generate app bundle >Create
Steps for sideloading the app package: enable your device for development -> install the signing certificate to the Trusted People or Trusted Publishers Certification Authorities store ->double clicking the app package file(Windows 10 Anniversary Update or later.
)
You could see more details in document:Create an app package upload file and Sideload your app package on Windows 10 Anniversary Update or later
I found the simplest way was to use VS2017 to create and assign the certificate. VS2019 has removed the UI, though it appears they are considering bringing some or all of it back.
Further reading can be found on this Visual Studio Developer Community discussion.
I have a UWP app. I'm using Visual Studio 2017 15.4.1. The UWP app is a store app and has been deployed to the Microsoft Store. My app was working fine in the store, and it was also working fine when I hit play in Visual Studio. Then recently, an isolated storage issue started occurring so I went in to the app in "Apps & Features" and hit Advanced Options -> Reset. Somehow this has fried my app installation on my machine. Our app no longer shows up as an installed app, and when I try to install the app from the store, I get an error with a code of 0x80073CF9. So, I can't uninstall, or reinstall on my machine. I've tried running sfc /scannow etc. to find out what's wrong, but nothing seems to help.
This wouldn't even worry me too much, but I can't even develop right now because when I try to run the app from Visual Studio, I get this error:
In order to debug this project, you must consume it from a Windows
Store app project that creates a package and is marked as the Startup
Project
I'm getting this error in the output window from the build
4>DEP0700: Registration of the app failed. [0x80073CF9] Another user
has already installed an unpackaged version of this app. The current
user cannot replace this with a packaged version. The conflicting
package is [APP NAME] and it was published
by CN=[Publisher].
What did I do wrong?
You can use Get-appxpackage -allusers *<appname>* | Remove-AppxPackage
The allusers option is important here.
You can also try to manually remove the content of the application cache folder in C:\Users\\AppData\Local\Packages\. If you have one locked file here, the whole deployment will fail.
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.
When I develop for Windows Phone, I am able to side load the current version of the app (version on the Windows Store) and then run the app in development in the same emulator. This give me an idea if the app update work.
I am trying to do the same thing with Windows 8 App but it doesn't work. I side load the current version of the app and then run the app in development and I get the following message: "The app ... is already installed on this machine".
How can I test the update path for my Windows 8 app?
Thanks!
When you build an app from the Windows Store it gets packed up into a an .appx file, which, you can submit for certification or side load using the PowerShell script.
When you run it in a development environment (pressing “play” in Visual Studio) it installs an unpackaged version in a different directory. What this means is that you must remove the packaged version before you can install the unpackaged one.
However, you can build a package and side load that one, as long as the version number is larger than the one already installed:
In Visual Studio, right click on your project and select “Store” and then "Create App packages...". When asked if you need to build the package for upload to the Windows Store, select "No".
Choose an output location and enter a version number higher than the one of the currently installed version
Wait for the project to build.
Start Windows PowerShell from the start screen, and navigate to the output directory from the above step
Navigate to the sub directory for the correct build of your app (eg. “MyApp_1.0.1_x64_Debug”)
Run .\Add-AppDevPackage.ps1 and wait for the app to install.
This will have upgraded your current packaged install to the new version, which will allow you to test that any upgrade code in your app works, you will not, however be able to debug it in Visual Studio.
Note, that when your done testing, you should use the remove-appxpackage <Your app ID> (Documentation) PowerShell command to uninstall the side loaded version to prevent you from having issues if you try and install a version from the Windows Store.
Hope that's helpful.
-Andy.
Update: I forgot to mention, you may have to run Set-ExecutionPolicy RemoteSigned from an admin PowerShell window before you are able to execute .ps1 scripts - http://technet.microsoft.com/en-us/library/hh849812.aspx