- What steps did you follow to create your key and upload to PGB?
- What kind of phone are you trying to install on? What version of Windows does it have?
- What emulator setup are you using?
You might consider using the PhoneGap Developer App (paired with the PhoneGap CLI) for the time being. This assumes that you are only using core plugins, however. Plus there are some edge cases where the PG Dev App doesn't work quite like you might expect (since it is itself a PhoneGap app), but it might get you moving while your situation w/ PGB is worked with.
1. I just added my Windows Phone Publisher ID in the dropdown where it says "add key". I see it in my account but I can't select it in the dropdown.
2. Lumia 435 with Windows 8.1
3. None - tried to install Visual Studio on Parallels Windows 10 but I have to have a Visual Studio project open (it seems) to run the emulator, and PGB only creates the appk file
Ok, please see Signing | PhoneGap Docs and make sure that your PhoneGap app is using cli-6.0.0 or below. If you aren't specifying this in your config.xml, you'll end up using a more recent version, which only supports Universal (Win10) signing.
I'm using a plugin that said to use this version:
Should I downgrade to 6.0.0 so it'll work on 8.1?
Yes, but if a plugin has said to use cli-6.4.0, there's no good guarantee that the plugin will continue to work. You may need to specify an older version of the plugin (if available) that works with cli-6.0.0.
I downgraded to cli 6.0.0 and rebuilt the app and selected by Windows Phone publisher ID, and I'm still getting "Can't Install Company App"
App ID is 2397835
Is there any way to debug this and see what the error is?
I'm not staff, so I can't see the details of your build, sorry.
I don't have a Windows 8 device to test on, otherwise I'd suggest DMing your build my way, but all my devices are Windows 10. Perhaps someone else around has one, though.
Can 8.1 apps be installed on Windows 10 devices?
I'm not sure, to be honest; I've never tried. My Windows PhoneGap experience, limited as it is, starts with Windows 10.
If you want to DM a link to me, I can try it on my Win10 tablet and see what happens, but I can't make any guarantees.
I got your package, and it does indeed try to install it, but I get the following message:
"Ask the app developer for a new app package. This one isn't signed with a trusted certificate (0x800B0100)"
This just seems to indicate that the package itself is unsigned.
Would you mind trying to install this version?
I imagine the same error will show but just wanted to see if what I did
helped (swapped out key)
On Wed, Jan 11, 2017 at 9:50 AM, Andy Milk <firstname.lastname@example.org>
Same exact message, sorry. :-(
How do I get the attention of PhoneGap Build staff?
It looks like it's a certificate signing issue, but I've followed the steps here for a Windows 8/8.1 device:
Why am I still getting errors that the app isn't properly signed?
I have the same issue. I have been using the same WP key with a number of different apps for a few years and now it does not show up.
If it does, by changing cli or phonehap version (such as 3.7) on config.xml, an appx (not .xap like I have always used) can be dowloaded, but Windows developer will throw an error such as:
Package acceptance validation error: The PublisherDisplayName element in the app manifest of Appname.Phone_18.104.22.168_anycpu.appx is Default Publisher Name, which doesn't match your publisher display name: Publisher Name. (fictional names)
1 person found this helpful
I seem to have fixed the issue using, in config.xml :
<preference name="windows-identity-name" value="27123Publisher.AppName" /> (also from your Windows Developer Account for the specific app)
Also, I have created a new publisher Id in the PGB control panel using the Windows Publisher ID as opposed to the Windows Phone Published ID (note the "Phone" part), which, again, can be found on the Windows Developer Account (dented wheel icon, Account Settings)
I have use cli-6.0.0 in this case
Do you have a copy of your config.xml settings? I'm trying the same thing and although I can build the app I can't get the app to deploy on a device or in an emulator.