I am an undergraduate and new here. I have developed a MP3 music player app (.NET c#) like Groove music.
I want to know that --- Is it compulsory to get a code sign certificate for my source code from a CA like Digicert, if I am going to publish my app on Microsoft Store?
But they're very expensive. Isn't that?
Thanks.
Related
I want to publish an electron app to the Window Stores and the cost Microsoft says is $19. Does that include code signing?
I heard code signing certificate cost a lot? Does that $19 cover it?
I created a progressive web app, and it works perfectly. It prompts for installation and it saves the link on the android home and it shows no url address bar.
Then I used PWA2APK (https://appmaker.xyz/pwa-to-apk/) to create an APK and deploy on play store.
Once built, I downloaded the assetlinks.json, added the certificate SHA-256 modifying the assetlinks.json in this way (I changed values):
[
{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "xyz.appmaker.pblx",
"sha256_cert_fingerprints": ["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","SHA256: BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
}
}
]
Then I pushed it online, and verified that www.exemple.com/.well-known/assetlinks.json show the values in the browser.
The package name is the same of the APK, and the SHA-256 is the Application signing certificate.
I also added icons, screen capture and all the necessary stuff. the total workflow is validated. So once deployed a version for an internal test, I expected it to work correctly, but it doesn't. The application is installed with a default icon, it shows the rl address bar and it has some load problems.
Did anybody experienced the same issues? How did you solve it?
Thanks.
I am part of the team that build this tool. And as for the question, this can be solved by removing SHA256 from following.
Before:
"sha256_cert_fingerprints":
["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","SHA256:
BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
After
"sha256_cert_fingerprints": ["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
This should fix the issues you had with the address bar.
And yes, feel free to reach out in support forum anytime. Happy to help and thanks for using PWA2APK
This is just speculation, but are you using Google Play App Signing? With Google Play App Signing the app certificate should be the one Google signs your app with, not the one you sign with to upload to Google. The documentation is here. Specifically it says, under step 3 of the "New Apps" section.
Step 3: Register your app signing key with API providers
If your app uses any APIs, you usually need to register the certificate of the key Google signs your app with for authentication purposes using the fingerprint of the certificate. Here’s where to find the certificate:
Sign in to your Play Console.
Select an app.
At the left menu, select Release management > App signing.
Copy the fingerprints (MD5, SHA-1 and SHA-256) of your app signing certificate.
If the API provider requires a different type of fingerprint, you can also download the original certificate in .der format and convert it using the transformation tools that the API provider requires.
If you get the SHA-256 as described above and put it in your JSON instead it might work.
Simply copy your sha256 key from play console and paste after your original key in "sha256_cert_fingerprints" and build and deploy.
After uninstall and install the app from playstore
I'm creating a Line-Of-Business application for Windows 8.1+
I've completed the Apple variation and haven't had any issues with distribution.
In regards to releasing for Windows I'm told I need to sign my application with a trusted root certificate.
From what I can tell I can get these from Symantic or Digicert (I'm sure there are more options too).
1) Can someone tell me exactly what this is and why I need it?
2) Do I need the standard certificate or the "Extended Validation" certificate?
3) How would one sign their application with this certificate after it has been obtained?
Thank you!
Yes with Windows Desktop app we are going with sing in application with "Symantic of Digicert" certification and etc.
But with Windows Store app here things are different you need to do "Associate app with the Store..".
Here are the steps for it:-
Do right click on your project from solution explorer >> Select Store >> then select "Associate app with the Store..".
By it it will automatically download all content from store.
Notes :- You have to do "Reserve app name on Store" first.
=> You need Developer Dashboard account for Windows Store for it.
Check attached image for 1 and 2 so you can get idea.!
=> It also will download "YourAppName_StoreKey.pfx" file in your project, which you require.
I just completed my windows 8.1 app and now I want to put it in the store. This is my first app publishing in the store so I want to know that how can I sign my app using self sign certificate.
I referred various Msdn articles but they points to signing certificate for that apps that are going to be sideloaded.
Currently I am using Test certificate which can be generated from app manifest file packaging tab.
Thanks in advance.
You don't need to - Store-submitted apps are signed by the Store itself.
This is a simple questions:
I've developed my first app for windows phone 7 (Mango). I have created a new release in the marketplace for beta test.
I have received one confirm email about this process. All is ok. But now, in this email, there is a Url like this:
zune://navigate/?appid=46546c45-7b41-11ae-b78e-268334559f0ac
In theory, I have to send this url to beta testing people of my list. But Where I or they have to write this url for download the app?
In zune? In the marketplace? I don't know what I have to do with this url....
Thanks guys,
JPe
When you submitted the app for beta testing, you needed to specify the live ids of some testers. This link (zune://) can be used to install the application through Zune. You need to send this link to those testers whose live ids you entered there. Just paste the link in any browser and it will open with Zune.
The link will not work for anyone else, but for the specified live ids.
If your live id is not in the beta tester live ids list, I am not sure that you can test the app with your live id. I'd suggest to add your live id to the list.
And by the way, you cannot access a beta app through the Marketplace, the only way is through Zune with the given link.
I hope it will work for you.
I have found in most cases the beta links only work when opened from a Windows 7 device, opening the link on a PC through Zune either gets a "app not available" or "app not available for your country".
There doesn't seem to be any setting in the marketplace to get around this so it may be by design.
No word yet on if this is fixed with the web marketplace but I doubt it since the Beta apps only give a Zune link