We develop an app which is on the Windows Store and targets Windows 8.1 in it's build. The app is fully submitted to the store and works perfectly on Windows 10 devices. However on all Windows 8.1 devices we are receiving the following message when trying to install the app from the store:
Purchase Error - Sorry, this app can't be installed because your PC might not meet some of the requirements. Go to the app's description page to check for any requirements listed under details.
The apps description page has no requirements other than supported processors of x86, x64, ARM. There is nothing special about the requirements for the app and we are not using anything out of the ordinary.
The app works fine if it is side loaded or remote debugged onto a Windows 8.1 device. It just seems that the Windows Store for whatever reason is incorrectly blocking its download onto any Windows 8.1 devices.
Has anyone any ideas? We have attempted a wsreset.exe without success.
Thanks,
Related
Background
I have developed a desktop application which runs on Windows 7 SP1 x64 and potentially newer OS, but for now I'd like to release it for Windows 7. It is not available for Windows Phone nor is it available in a store. It's a good old standalone program, no cloud, nothing special.
At the moment I have some trouble, because the tool says
The Windows App Certification Kit did not detect any new applications as a result of your installation.
Testing cannot continue unless an application is successfully installed.
Please confirm that your installer worked correctly and run the Windows App Certification Kit again.
I'm working on that and I hope this will finally not be related to the question.
My Research
From the statement
The Windows App Certification Kit now supports the following app types: Desktop apps for Windows 8.1, Windows 8, Windows 7
on Windows App Certification Kit, my impression is that Windows 7 is supported.
However, on Using the Windows App Certification Kit, Windows 7 is only mentioned in a weird scenario of testing a Windows 10 app on Windows 7.
The website Certification requirements for Windows desktop apps talks about "Windows 8.1 Desktop App Certification" and refers to Windows 7 only for the name change:
[...] in order to participate in the Windows 8.1 Desktop App Certification Program. For Windows 7, this program was known as the Windows Software Logo Program.
The Question
Can a Windows 7 desktop application still get certified?
related:
What do I need to do to submit my desktop app to the Windows Store?
The main advantage to get a desktop application certified is that it can appear on Windows store.
Windows 7 cannot access Windows store, therefore it's pointless as far as Windows 7 users are concerned.
Windows 8 can access the app store, but it doesn't really work for desktop apps. User must exit desktop-mode and enter tablet-mode, go to Windows store, find the desktop app. But the desktop app will only appear as a link to developer's website. User must go back to desktop mode, go to the link and finally install...
Windows 10 allows users to install desktop apps directly. However there is not enough information yet.
As to your question, there is really no such thing as Windows 7 application. Maybe you made your application on Windows 7, but it probably runs on Vista, Windows 8, and 10. You just have to test it. It can get certified for Windows 10, but I don't think it will be the same way as Windows 8.
Problems with certification kit: Make sure the your application is completely uninstall from your computer, including app installation folders and app registry keys. Run the test again and make sure the program was installed.
I have a project that runs on Windows Phone 8 and Windows Phone 7.5.
It works fine on 8 devices in all cases, but on Windows Phone 7.5 it crashes on startup with following message (only if installed from store):
If the application is built on PC and uploaded to device it works fine. I tried numerous things but nothing helped.
Looks like it was a store issue. Should be resolved now.
Issue with 7.1 XAP submissions between Dec 04 and Dec 12 (Beta and Non-beta apps)
Well, my assumption is that your XAP file does not contains all the DLLs needed. Make sure the references to those DLLs indicate CopyLocal=True. Also it would be nice if you can share the beta link to check your stack traces.
P.S. this may help:
Troubleshooting Windows Phone App Problems that occur after Submitting
Your Windows Phone 7/8 application tests fine, but fails after publishing to Marketplace or after private app distribution
I guess it's a problem with the Async pack binding. You might want to try to remove the package and readd. More below:
Async Targeting Pack troubleshooting
In the past I was able to repro many post certification issues just by run the release version of the app from Visual Studio and simply unplug the cable while it is running. Sure you can't debug it but at least you can repro and test it without submitting it.
Thank you guys for your advice, but error has gone away. I don't do anything, i think that it was something with store...
I have to develop a mobile application for windows mobile and NOT windows phone.
I am trying to initialize the development environment in Windows 7 OS 32/64 bit.
I searched the web for environment initialization.
Please let me know the environment initialization procedure for Windows mobile application develoopment in Windows 7 32/64 bit from scratch.
Any help is greatly appreciated.
I dont understand the question.
I had to do nothing special as I installed Visual Studio 2008 and then the Windows Mobile 6 SDK.
I assume, you already connected the WM device to your Win7 station. So you should have WMDC already installed. Otherwise install Windows Mobile Device Center from the MS site.
Secondly install VS2008 (not express version, it does not support WM development).
Then download and install Windows Mobile 6 (professionell) SDK and install.
That is all, nothing special. I did it without any hassle on my Win7/64 PC. Should be the same for Win7/32.
If you need further assistance be more specific in your description.
I installed Visual Studio 2012 and Windows Phone 8 SDK successfully. I created a new phone app and trying to run but it doesn't show me any emulators in Visual Studio 2012.
Make sure that your PC satisfies the system requirements for running the emulator:
Windows 8 Pro edition or greater
A processor that supports Second
Level Address Translation (SLAT)
If your computer meets the hardware and operating system requirements,
but does not meet the requirements for the Windows Phone 8 Emulator,
the Windows Phone SDK 8.0 will install and run. However, the Windows
Phone 8 Emulator will not function and you will not be able to deploy
or test apps on the Windows Phone 8 Emulator.
Source
Pretty much #Olivier's answer. Also, make sure you have Hyper-V enabled on your computer.
In lieu of this, There's a very nice tool on codeplex that pretty much checks if your computer is able to start hyper-v and the windows phone emulator.
If that passes, you'll want to follow this article in order to get hyper-v set up. Specifically the two enabling sections.
There was a post a little while back on what is required specifically here on stack overflow. It can be found here
I'm getting an error when I start up the windows phone emulator:
windows phone emulator not supported because your computer does not have the required graphics processing unit configuration. An XNA framework page will not function without a graphics processing unit. Do you want to continue starting the emulator?
And when I attempt to access a web page (any web page) - I just get a blank screen. How do I resolve this?
I'm running windows 7 on a mac.
Check out the system requirements for the emulator on MSDN.
Start by updating your graphics drivers to the latest available. If that doesn't work the next step would be to upgrade the graphics card, if you can.
A PC which won't run the emulator can probably still be used to develop and debug on a real device.
It may be you're also trying to run the latest SDK 7.1 which is far more restrictive than 7.0. If you find yourself unable to run 7.1, dropping down to 7.0 may work on your particular machine.
If you are running Windows 7 on a Virtual Machine on Mac OS X it won't work because there are some restrictions on running a Virtual Machine inside a Virtual Machine.
The quick and easy solution for this is installing Windows 7 in bootcamp, it worked for me.