I get this error when uploading the msix to the store:
Package acceptance validation error: The package Documents002.msix doesn't contain any Application elements in the app manifest file.
and another error, that dont uderstand:
Package acceptance validation error: The PublisherDisplayName element in the app manifest of Documents002.msix is Javier Gastón, which doesn't match your publisher display name: Javier Gastón.
I'm using a .py that I've passed to exe, after that I made it installable with Advance Installer Express, and after that I used microsft MSIX Packaging Tool, (so I've not used vs for the proy).
How can I solve this problem?
I expect to solve this and manage to upload without errors the app to the Windows Store
Related
I am trying to upload a windows phone app on store. The previous version which was uploaded is 4.0.0.0 and the new package which I am trying to upload is v4.1.0.0.
As per my understanding v4.1.0.0 is higher than v4.0.0.0. I dont understand why I am getting the below error
Error message from Windows :
You’ve uploaded another package with the same properties as this one. When this submission is published, the other package will replace this one.
This package (4.1.0.0) will be removed after you save this page because you have a higher-versioned package that supports the same customers.
I think you need to remove the package v.4.0.0.0 manually and save only v.4.1.0.0
I have an integration services project in which I use a script component as a source. In the script I read data from a Google sheet and in order to do that I have to authenticate using oauth protocol. I tried to make the necessary references using NuGet but receive errors and have been told that NuGet does not work with SSIS. I have tried to manually make the references and the script builds but when I run the package I get this runtime error:
Could not load file or assembly 'Google.Apis.Auth.PlatformServices,
Version=1.9.3.19383, Culture=neutral, PublicKeyToken=4b01fa6e34db77ab'
or one of its dependencies. The system cannot find the file specified.
Any ideas on how I can get this to work?
I was able to clear this error by adding all dll's in the NuGet package into the GAC and then referencing from there. I then faced a version dependency error which I overcame by adding a binding redirect in my machine.config. Not the most elegant solution but I just needed to make it work and other methods I tried weren't meeting with success.
I am working on a Windows Phone 8 project where we are deploying it as a company app through HockeyApp. I have a .PFX file generated from our Symantec cert and the correct .aetx file installed on the device.
If I take the .XAP file I intend to deploy and copy it somewhere separate and test it by deploying it using the XapDeploy.exe tool, it will install silently and work properly. Then I use the XapSignTool to sign the .XAP against the .PFX successfully ("XapSignTool Success: Successfully signed = C:\xxx").
When I attempt to test this recently signed XAP with the XapDeploy tool I will get the error "Error - Installation of the application failed. Run time error has occurred. Fix the Capabilities in the WMAppManifest.xml file." If deploy this file with HockeyApp the install will silently fail on the device and appear to just sit there after download.
Does anybody know what could be causing this after code signing?
I was able to resolve my issue. First, a codesigned XAP will not run in the emulator unless you have already installed the AET file on that current running version of the emulator. So, it was incorrect for me to to expect not to see a failure after the XAP was signed.
I then encountered some other issues when deploying to my device. This was resolved by making sure that the Publisher ID GUID was the same as the Publisher ID used for the Symantec cert.
Also, as opposed to using the XapSigningTool directly I ended up using the PowerShell script that runs both the MDILXAPCompile and signs the XAP in a single step (making the post-build step easy to write). The ps script BuildMDILXap.ps1 is found under \Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\MDILXAPCompile\ and ships with the SDK apparently.
I have now followed all the Blackberry documention found here and here. Yet some how I keep getting the following error:
[BUILD] Populating application source
[BUILD] Parsing config.xml
[BUILD] Generating output files
[WARN] Failed to find debug token. If you have an existing debug token, please copy it to %HOME%/.cordova/blackberry10debugtoken.bar. To generate a new debug token, execute the 'run' command.
[WARN] Failed to find debug token. If you have an existing debug token, please copy it to %HOME%/.cordova/blackberry10debugtoken.bar. To generate a new debug token, execute the 'run' command.
I have created the bar using this link here (which wasn't even specified in the links above) Please can anyone explain this or point to a tutorial the gets one up and running to a hello world app for blackberry WebWorks as the Blackberry links really don't help
I've not been able to find useful instructions either, however I have the native SDK installed alongside the Momentics IDE and it has a wizard that created all the necessary for me:
Create a new BB10 project
Right click on the project root node in the Project Explorer
Open BlackBerry Tools and then Configure Targets
A wizard will start allowing you to create the CSK and BAR files, and also deploy them to your devices if there is no CSK in C:\USERS[User]\AppData\Local\Research In Motion
If the CSK already exists in the path above you'll be able to create and install Debug Tokens with your existing CSK.
After you've created the token I had to copy it to C:\Users[User].cordova and rename it to blackberry10debugtoken.bar to get the build in the WebWorks UI to work.
However, though I've now got an installed DebugToken on my simulator, and the Webworks UI happily builds the project, the Build and Install action fails with an error message as follows:
fs.js:418
binding.open(pathModule._makeLong(path),
^
TypeError: path must be a string
at Object.fs.open (fs.js:418:11)
at Object.fs.readFile (fs.js:206:6)
at _self.findConnectedSimulator (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\lib\target-utils.js:190:12)
at Object.async.series.ip (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\lib\run-utils.js:48:17)
at D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:561:25
at iterate (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:131:13)
at Object.async.eachSeries (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:147:9)
at Object.async.series (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:560:19)
at Object.getTargetName (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\lib\run-utils.js:45:15)
at fn (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:579:34)
I'd be grateful for anyone who is able to further my discovery and make the WebWorks UI work without having to install Momentics & the native SDK, or to get the deployment to the simulator working...
I have a native dll that I'd like to use in a WP8 project that I'm working on. I've done some research and have created a C++ Windows Runtime Component (WRC) to wrap the native DLL. The WRC project uses a .lib file, and my WP8 application calls the WRC project.
My solution compiles all fine, but when my application makes a call to a method in the native DLL, I get a The specified module could not be found. (Exception from HRESULT: 0x8007007E) exception.
From reading around it seems like the dll is not being loaded. I've copied all relevant dlls to the output dir of where the .exe file is and also in various places but the error keeps showing up.
If anyone could point me in the right direction I'd be very grateful. Also if more info is required I'll post that up also.
The DLL must be included in your XAP package. Something you can see being taken care of in the Output window when you build your app, it starts with the "Begin Xap packaging" messages and then lists all the files that get added. The runtime error says it is not being included.
There is remarkably little guidance on how to ensure that a file gets included in a phone package when MSBuild cannot figure out the dependencies by itself. It certainly won't for your DLL, no way the build system can tell if it isn't a project in your solution. Seems you're operating a bit on the bleeding edge in this case :)
But this works well when I try it, going by the MSBuild output and not by actually testing it: Project + Add Existing Item. Navigate to your DLL and select it. Select it in the Solution Explorer window and look in the Properties window. Ensure that "Build Action" = Content, Copy to Output Directory = "Copy if newer". Rebuild, you'll now see the file getting added to the XAP. Which should solve this particular error. There might be others :)
Windows Desktop or Windows Store native DLLs are not binary compatible with Windows Phone, even if they are built for the same CPU architecture.
Therefore you will need to recompile your native DLL for the Windows Phone toolset.
About Windows Runtime Components:
On Windows Phone a Windows Runtime Component is itself a native DLL (.NET is not supported on the phone). The binaries of Windows Runtime Components cannot be shared between Windows Store apps and Windows Phone apps.