I prepared a simple quiz app for Windows 8 store. My app successfully passes on WACK just after building and creating local packages without login to store account, however it fails (perf test: launch was not detected) when I login to my store account, associate the app with a reserved app name and create packages to submit.
So, I submitted my app three times and it always failed requirement 3.8 since those packages fail. What should I do? Is there anything I miss? I'm dealing with this issue for many days but I can't find the right solution.
Regards,
Hakan
I downloaded and installed Visual Studio 2012 Update 1. WACK tool I use is the latest one. My Windows 8 account and Windows 8 Store account are same. However; I still have the problem.
That's what I'm doing;
I recreated my app project. Successfully builded the app and created (not store associated) app packages without login to store account on Visual Studio. After creating those packages, I started WACK on Visual Studio and app passed successfully. Then; I cleaned the solution and created the packages to upload store (I logged in to my store account on visual studio and chose the app name I reserved). After creating packages I started WACK again, but this time app failed with; "Launch was not detected" error.
I don't think there is anything else to do. I get bored after each unsuccessful submitting. What should I do? Does anyone have any idea?
Requirement 3.8 is very specific, and has nothing to do with your app's name. From the App Store Requirements:
3.8 Your app must meet the basic performance criteria on a low-power computer
The app must launch in 5 seconds or less
The app must suspend in 2 seconds or less
Did you test your app on an ARM based device? How much time does your app take to start up/ suspend?
Update:
If you are using the standalone WACK, it is possible that you are trying to certify the old version of your application. As I recall, when you associate your app with the App Store, your app's name AND package ID change. However, bits of the old app may still be around, which can cause the certification to be run on an app that no longer exists.
Something that may help is to first uninstall your app prior to creating the package. The other thing to try is to run the certification from within Visual Studio. I have found it to be more reliable than the standalone app.
Related
I cannot select the latest version I have uploaded to seed to beta in external testing. First of all whenever I upload a build two version appearing, that have upload time difference of 5 to 15 minutes between them. One of them gets changed from processing to normal available state, but other does not. But now selecting the available build also selects the processing one and my selection is blocked and I cannot select the OK button because probably my selection is blocked by the processing one. I think it is UI frontend issue at itunesconnect side but it could be something I am doing wrong. Please help me if anyone has been able to tackle this issue if they faced. Please see checkout the attached image.
Update:
I Included <key>ITSAppUsesNonExemptEncryption</key><false/> in my subsequent builds that I uploaded according to the new Export compliance message on the iTunes Connect home page. I am still facing the issue. I have contacted Apple Dev support, will keep you updated if I find a solution.
The issue has been mysteriously solved by uploading the application from Application Loader with Aspera turned off instead of using Xcode's organizer window as suggested by Apple Developer support. Make sure you add: <key>ITSAppUsesNonExemptEncryption</key><false/> in your info.plist file before archiving the build. Although mysteriously my previously uploaded builds have also become available for external testing.
Body of email that helped solve the issue:
After further research, it looks like their may be an issue from your
end with your network while trying to upload to this app record in
iTunes Connect.
First, for the best upload experience make sure that all ports and IP
addresses are accessible. Additionally, it’s important to make sure
the internet connection is very good, and that there are no firewalls
blocking the uploads. More information can be found here:
http://help.apple.com/itc/apploader/#/itc8e7ec5a60
Second, it may be beneficial to try using the latest version of
Application Loader. Please note that you can export your project from
Xcode to upload through Application Loader. As a temporary workaround,
once you have Application Loader open, you can go to the File menus
and select the following:
Application Loader > Preferences
Then, select Advanced, and as a temporary workaround you can try
deselecting Aspera and upload the build again. You can follow the
steps below to use the latest version of Application Loader.
Download the latest version of Xcode from the Mac App Store:
-http://help.apple.com/itc/apploader/#/itc8e7ec5a60
Open the latest version of Xcode
Go to the File menu and select Xcode > Open Developer Tool > Application Loader
Lastly, try uploading again to see if the issue persists.
Hello my dear friend there,
I am also having your issue yesterday, I have this similar screen with yours:
The build is duplicated which one of them are processing forever until today.
My personal problem solving was:
Increase my build number in Xcode so that I can reupload my build
Rearchive the build then export for iOS App Store Deployment in Xcode Organizer
Reupload the build using Application Loader
Then try to reconfigure the build in iTunes Connect. For a while it is processing like usual, but it will not take forever, after one hour, the build will be available for testing.
Hope my personal troubleshooting can be applied to your issue too.
I have version 1 of my Windows Phone App (w8.0) in the store which has been running for a while now. The app uses a SQL Server compact database for local persistence on the device.
I'm now ready to release v2 of my app (w8.1), which has a number of database schema changes. The question is how I can formally setup a test environment for the test team where testers can:
1...Install v1 of the app from the store
2...Run it up and do some light activity
3...Then upgrade the app on the phone to v2
4...Continue testing using an upgraded version of the database
Up to now all v2 testing has been done using a shiney new install of the app.
I know i can do this using Visual Studio, but this defeats the objective of the test i.e. a live user upgrading via the store.
I've tried using the app deployment tool, but this deletes v1 of the app (including the database) when it deploys v2. I was surprised it did this - I thought it would recognise the install as an upgrade. I can verify this because it deletes the database. I am using the same names/keys in the manifest, including an incremented version number.
For now I have a new (hidden) TEST app in the store where i've submitted v1 of the app. Once the testers are ready, I submit v2 of the app to the store which the testers then upgrade. Problem here is that it takes upwards of 12 hours for the store to publish the upgraded version.
I am aware that you can install an app from the SD cards, which is pretty close. Has anyone else found a good elegant way to do this?
You could use Windows Phone Power Tools to achieve this.
Here's the link: https://wptools.codeplex.com
Just install the old xap, do some stuff and then update to the new xap using the "UPDATE" button. If you don't change the app ID, it will surely work.
Hope this helps! :)
I try to build a metro-style-app with Javascript and when I run the Windows App Cert Kit (WACK) Certification tool the test always fails on the performance test with the following message:
Following errors were detected when tested the byte code generation:
This package was made available for the development or Authoringmodus. Uninstall the package and reinstall it in the normal way.
I’m using jquery and some jquery-mobile libraries inside my app. Is that the problem? The error doesn’t make sense for me, because it doesn’t say which package I should reinstall. I also try to uninstall the App itself (by right click onto the app) and build it again in the Release-Modus of VS2012, but the WACK tool always prompts this error :(
Find out that the WACK Tool allways shows this error if you don't run Store -> Create App Package and select "No" and press the next button. After that the WACK-Tool is started automatically and it passes the bytecode generation.
First save the all javascript files with encoding utf 8 format with signature
then create the app package
http://msdn.microsoft.com/en-us/library/windows/apps/hh975357.aspx
then if u already install the latest windows app certification kit then u will be able to see run with windows app certification kit button after creating app package .
My temporary developer license (using Visual Studio 2011 Beta and Windows 8 Consumer Preview) expired and a popup asked me to aply for a new one. This all seemed to work, but when I build and deploy to the local machine it takes me to the app store and tells me that the developer license has expired.
I've tried:
Unistalling my app from the home screen
Cleaning my project solution
Removing my developer license using powershell command Unregister-WindowsDeveloperLicense and getting new license again
Restarting machine
I can create new projects that build and deploy fine, but my existing project is stuffed. Is the old licence cached somewhere and how can I get it to forget about it.
There is this similar quesion on MSDN. Someone managed to solve it, but there solution has not worked for me and there are other people saying it hasn't worked for them.
The first month this happened to me, a reboot solved it. The second time it didn't. I went into my package manifest and changed the package ID. It looked like a GUID and I just put kmg on the end. Then everything worked fine. Later I tried changing it back but it failed again so I guess my package ID ends in kmg now :-)
I believe it's because you're trying to overwrite a package that was shipped by a "different developer". They're going to have to fix that somehow but hey, this is what betas ^H^H^H^H^H previews are for, right?
i'm looking for a way to manage application upgrades for my compact framework app.
let's say i have v1 of the app installed on my device, and v1.1 has been released. I want the app to make a call to my server to see if there is a new version. since a new version is found, i want to send down the new version of the app to the device and have it installed, replacing the old version.
my first thought was just to have the app download the .cab file and kick off the cab file just before exiting the app. this would mostly get the job done but it would prompt the user to pick the installation location if they have a storage card or other partitions on their device. i would like to prevent any user input and just have the new version of the app installed, replacing the old app.
i'm certain that there are others doing this already and i don't want to reinvent the wheel, here. what application management tools and systems exist for this type of process? how can I facilitate this type of process?
...
EDIT:
in spite of my previous searches before posting this, i just now found this question: How to Auto-Update Windows Mobile application
When I wrote one I relied on launching the .cab file. It was definitely the path of least resistance.
Otherwise, I'd write a simple "upgrade.exe" executable that gets distributed with your app. When upgrading, you'd download the new package, launch your upgrade.exe just before exiting your app, then have that program copy over the new files to your app.