I am new to Windows 8 application development, I have created the package and I have tested by launching Windows Store Test Kit. It has passed the test, but while uploading the package to the store, its showing three four errors.
Validation error: All packages for this app must use the package identity name
Validation error: The following display name doesn't match any of your reserved names
Validation error: The PublisherDisplayName element in the app manifest doesn't match your publisher display name
Validation error: The Publisher attribute of the Identity element in the app manifest doesn't match your publisher ID, which is: CN=XX-XX-XX
I tried by uploading the different projects with different names, but I am getting the same issue. I am using Visual Studio 2012 to create the package.
Please help me to solve the issue.
Thanx in advance.
It looks like you did not associate your app with the store.
Right click on your project in visual studio
Go to Store
Then Associate App with the Store...
Follow instructions
It will update your application manifest according to Windows Store requirements.
Once it is done, you can create a new package. Make sure you check the store deployment option during the generation wizard.
Hope this helps.
Related
I try to send an update for my app to Windows Store by Windows Dev Center Dashboard, this update contains 3 packages: 2 for Windows 8.1 (Desktop and Phone) as a bundle and 1 for Windows 8.0 that does not support any bundle.
Before the new dashboard the package for Windows 8.0 was accepted too in this configuration... not now and it reports this error:
A previous submission for this app was released with a Windows Phone 8.1 appxbundle. Subsequent submissions must continue to contain a Windows Phone 8.1 appxbundle.
but it isn’t a Phone package and for Windows 8.0 I can’t make a bundle! there is a solution? with the old dashboard that worked great.
Best regards,
Claudio
Not sure if it is applicable here. But in my case I've got the same error when updating UWP version of the application on the store where I had UWP, WP81 and W8.1 apps. The error was signaling the fact that the existent store UWP package was build with as a bundle but the new package was not.
So the solution was to replace in .csproj the <AppxBundle>Never</AppxBundle> with <AppxBundle>Always</AppxBundle>. If you publish from Visual studio directly you can do that from UI as described here.
I had this problem. I deleted all the files in the folder where the package is building to the store. Then I created a package for store. This problem is solved.
I had the same error message appearing from nothing (just making a new build, no changes to platform). When I checked the box "do not automatically increment" (in UI, lead to <AppxAutoIncrementPackageRevision>False</AppxAutoIncrementPackageRevision> in csproj) and filled in my own number, the package that came out was called:
1.3.0.0_AnyCPU_bundle.appxupload
If I did not do it it looked like:
1.3.0.17_AnyCPU.appxupload
The latter did not work for some reason. So setting own build number fixed this particular problem for me. Why it fixed it? No clue.
I am trying to upgrade worklight project built using v6.1 to v6.1.0.01 and getting following error :
An internal error occurred during: "Upgrade Worklight Projects".
com.worklight.upgrader.versionGraph.VersionGraph.isKnownVersion(Ljava/lang/String;)Z
The version of studio is 6.1.0.01-20140418-0637
This could happen if your imported project is missing
either the complete org.eclipse.core.resources.prefs file in the .settings folder of your project (this is hidden file; you can see it using the Navigator view in Eclipse for example),
or if this file exists but it is missing the wl_version property.
You can fix this by creating a new project and copy over this file to your 6.1.0.0 project and then try to upgrade again to 6.1.0.01 - which you should be using 6.1.0.02 anyway by now and not 6.1.0.01.
One workaround you can do is to create a new project with the same name, etc in the Studio belonging to 6.1.0.01 and copy over your web resources and native code to the newly generated files.
You can also take a blank app in 6.1.0.0 and try to import that one to 6.1.0.01 to see whether it fails still or not. This will help in focusing the issue.
I am using ASP .NET MVC 4 with Entity Framework 4.5
I downloaded the nuget something to be able to export my data pro PDF and found one called RotativaW7. The project is working normal but I try to check in the project to publish to TFS and is giving the following error message:
ERROR: Multiple errors occurred during the operation, the first of which is displayed below. A full error list is available in the Output Window.
..\packages\RotativaW7.1.5.4\RotativaW7.1.5.4.nupkg: Unable to write data to the transport connection: The cancellation of an existing connection was forced by the remote host.
nuget:
Install-Package RotativaW7 -Version 1.5.4
Could anyone help me solve this problem?
The nuget package contains an .exe, are you sure TFS allows you to check in executable files?
My app(windows 8 metro, using javascript) uses indexDb for database, i have seen when i modify manifest file indexDB database is deleted.
Is this a bug or a feature??.
Now my app is already in windows store I am afraid if i will modify manifest file (which i want to do) users database will get deleted and that will be a huge loss to the user.
So what is the work around for this problem.
You can try their official demo and you will find the same problem
http://code.msdn.microsoft.com/windowsapps/IndexedDB-sample-eb1e95af
This is not a bug - when you modify manifest and deploy app using Visual Studio local data is cleared. This behavior is the same for JS, C++ and C# projects.
It will not happen to your users when they will update the app through the Store.
I'm creating an application which uses the RazorPDF nuget package for creating PDF document. When using this on a local development pc everything works fine but when I deploy on a server, I always get the standard error: "Error. An error occurred while processing your request."
Do I need to change properties in my project to make the nuget package work on a server except the normal way to deploy or has any one got experience with this?