I am preparing my app for upload to the MS Store and am running into problems with the Windows App Certification Kit. Nearly every test performed by the kit produces the exact same FAILED test result as follows:
"The selection criteria did not match any tests.
No test cases were executed."
My app is a Windows Forms app that was packaged using the "Windows Application Packaging Project" in Visual Studio 2017 (i.e. using the latest iteration of the MS "Desktop Bridge").
I should also add that I was able to successfully install the app bundle (.appxbundle) by loading the temporary cert and double clicking on the appxbundle so I know the UWP install works perfectly.
Any ideas on how to fix issue?
Thanks!
I found the solution to my problem! It appeared to me based upon the test result text that the Windows App Certification Kit was simply failing to run any tests at all...so I decided to uninstall then reinstall the Windows Software Development Kit (which includes the Windows App Cert Kit among other things). After reinstall the Windows App Cert Kit ran correctly!...AND MY APP PASSED EVERY SINGLE TEST!!! YES!!!
Anyhow, if you experience the same problem as me, you now have the solution to your issue...uninstall then reinstall the Windows Software Development Kit.
Related
hi I have been created an app at Xamarin form and I want to publish them to the apps store
on the google play store that was very easy
the problem of how to publish the app on apple store if I have just windows
I know that I have to use Xcode and just on mac
I think there is some way to do that from windows
Well in fact you could do it without a Mac, installing a Virtual machine as shown in this video, after that, you should be able to download the last version of Xcode through the App store within the Virtual machine. Then, within Visual Studio in your Windows, connect with your just created Catalina VM.
After that, you colud use Testflight instead of publishing the app directly on the App store in order to build beta tests.
Regards.
When I just installed a Visual Studio 2017 and created my Xamarin.Forms application, it ran fine on my Windows 10 PC. However, I then installed some apps from Steam (which is the only thing I can think of that could change system settings). After that, when I try to create another Xamarin.Forms project, it does not deploy well to my machine and gives the following error:
DEP6200: Bootstrapping failed. Device cannot be found.
SmartDeviceException - Deployment failed because no
device was detected. Make sure a device is connected
and powered on. [0x80131500]
Strangely enough, my first app continues to build and run fine, even if I uninstall it from Windows and then deploy it again.
What could be the issue?
I have just noticed that Visual Studio makes ARM the default architecture. Changing it to "Any CPU" brought back the option to run the app on my machine.
I am using visual studio 2017, created a new xamarin forms project and tried to run the UWP project. It shows the following error:
the project needs to be deployed before it can be started. verify the project is selected to be deployed the solution configuration manager, or deploy it explicitly by clinking one of the deploy commands in the build menu.
I have looked at all online solutions and only found that you need to set the cpu to x86 and to check the deploy checkbox under the configuration manager under the solution. Both these options don't work. I still get the same error. I have also tried every cpu option including ARM.
Have you tried to uninstall the existing UWP app from the Windows Start menu > All apps? Then deploy again from VS. It did the trick for me.
Sometimes when I create an app packet for win store; Visual studio seem to get hung up building to the packet (project needs to be deployed before it can be started -error).
I solve it by creating a new app packet.
We just started creating cross platform mobile apps using "Visual Studio Tools for Apache Cordova".
I followed the procedures described in Install Tools to Build for iOS and To run your app on an iOS device. Everything works nicely, the app gets deployed on my USB attached iPhone and runs as expected.
I then tried to upload the app to iTunes, to provide the app via TestFlight to testers and to generally see how app-submitting works:
Build the iOS app as "Release" in VS: it builds and deploys to the iPhone nicely
On the Mac: Start Application Loader, click on "Deliver your App" and navigate to "...remote-builds/builds/"xxx-buildnmb"/cordovaApp/plattforms/iOS/build/device/APPNAME.ipa"
Several checks run OK ("verifying assets, etc.), but it then stops with the error
ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle xxx.yyyyyy.zzzz [Payload/xxx.yyyyyy.zzzz.app] is invalid. [Missing code-signing certificate.] For more information, visit the iOS Developer Portal."
I then discovered the Xcode Project in ".taco_home/remote-builds/taco-remote/builds/<build-number>/cordovaApp/platforms/ios/" and used Xcode to define the code signing identities in "Build Settings" and the Team information in "General", created the archive via Product-->Archive and submitted it in the Organizer - Archives. And voila it worked!
My questions:
Do I have to use Xcode to submit?
If not, what might I be missing in a) regard to building and signing apps with vs-mda-remote, and b) submitting it with Application Loader?
What are Microsoft's plans in regard to providing access the build settings from within Visual Studio (similar to the ones in Xcode)?
Thanks a lot for any pointers in the right direction.
Thomas
You need to use distribution provisioning profile to sign the package and apps are published to the App Store by using the iTunes Connect website along with the Xcode Archive Tool, which is included with the iOS SDK.
I am using SQLite.WP80 version=3.7.16 in Windows phone 8 project.
Now when I tried to test with store test kit it says:
"the application package(XAP) is not up to date,recompile and try again.
change the solution configuration to release and platform to any cpu and rebuild the app"
But as I am using sqllite i cannot change to any cpu.
Can anyone tell possible solution?
You should target just one CPU during development (depending on what machine you will be testing/debugging on). When it's time to publish your app, you can select multiple packages, one for each CPU architecture. Visual Studio will then create several packages, which you can upload to the dev portal.