UWP app -Invalid package family name, after update certificate - certificate

I created app for uwp (win 10 desktop). I could not build package for store. I received an error: it is necessary to update the certificate. I have updated certificate and build my package. But when I upload the package to the store, I get the error:
Invalid package family name: MyPackage.xxxx_xxxx (expected: MyPackage.yyyy_yyyyy)
Invalid package publisher name: CN=XYX (expected: CN=xxx-xxxx-xxx-xxxx)
But I opened my app manifest and I see:
Published: CN=xxx-xxxx-xxx-xxxx
Package Family Name: MyPackage.yyyy_yyyyy
It is what expected. In "open sertificate" I see : Publisher -XYX.
How do I fix it all? Any ideas?

I solved this issue. I made a mistake when creating new certificate.
It must be so:
Open Package.appxmanifest.
Go to the "Packaging" tab.
Copy Publisher DN(number after CN=)
Click the button "Choose Certificate" and select the item "Create test certificate..."
Copy the publisher DN from step 3 to the first editable text field

Update for Visual Studio 2019
Open Package.appxmanifest from Solution Explorer
Go to "Packaging" tab
Copy Publisher name after CN=. Looks like a GUID
Click "Choose Certificate..."
Click "Configure Certificate..."
Click "Create..."
Paste GUID from #3 into "Publisher Common Name"
Proceed to create and save certificate
Problem seems that it defaults to developer name instead of using the original GUID

I found this MSDN blog: https://blogs.msdn.microsoft.com/jamiedalton/2017/01/13/windows-store-error-updating-package-invalid-package-family-name/
The blog states that you should associate your App to the Store App using Visual Studio.
This seems to be the right answer.

For us, the problem was that we tried to publish the app before associating it with a submission. The fix was the following:
Delete the temporary key .pfx file at the root of the directory
Re-associate the app with the store via the Publish menu

Related

Visual Studio 2017 ClickOnce - Unable to view published application

I have an application that I'm trying to publish to my website. The error I'm getting is that when done publishing, it says:
So it looks like it succeeded, but didn't.
My website is located at www.mywebsite.com.
In my build properties, under the publish tab, I click options->deployment, then set deployment webpage title to 'rdl', then I check automatically generate deployment webpage after every publish
I then go through the Publish Wizard:
Specify the location to publish this application: ftp://www.mywebsite.com/
Click next.
Check From a website: Specify the url: http://www.mywebsite.com/
Check Yes, this application will be available online or offline
The final page then states:
The application will be published to:
ftp://www.mywebsite.com/
Users will launch this application from:
http://www.mywebsite.com/
Click Finish
I am then left with the error described in the image above.
When I go to cPanel (my web host), I am able to see the Application Files folder which includes my application folder inside it.My .deploy and .application file are also located there along with any assets I had.
This Application Files folder is on the same level as the public_html folder if that matters.
Any help would be appreciated, I'm not exactly sure where I'm going wrong!

Can't create new sites and pages in Teamsite

I've just installed Teamsite on Linux CentOS 6.5. I've used Silent Installer and mostly default properties (install.properties), I logged in as a root user and everything seems to be good but the problem occurs when I'm trying to create New site or New page. I click as a usual File -> ... and there is only New File, New Branch etc. but there is no New Page or New Site button. Do you know what could went wrong during the installation or what can I do to "restore" this buttons and create sites/pages? Thx.
Ensure you are under a Workarea. Create a workarea under a branch and give it a try.
If you are already under a Workarea, then this would the issue with your license. Have you generated right licence from the official license website from HP Autonomy.
The Features are tied to License what you have. Just to cross verify if you do not see SiteMap TAB next to Content and Workflow ( just above file menu ) that indicated you are missing a full licence.
Please generate new licence and try deleting old and start Teamsite server issuing iwreset -a command.
Let me know if this helps.

release an iphone application

i try to generate a nameproject.app after the build/Release.the build has succeed but i didn't find the file nameproject.app under product !! (it seems to be availble but the option "show in Finder" is disabled ) . My question is how to generate nameproject.app?
You will need to Build and Archive your project. You may need to check what code signing settings you have in the project and executable.
Use the Organiser to select your archive version and then you can Share that version of your project. You will need to select the correct code signing again. It will allow you to save the .ipa file where you want.
Drag and drop the .ipa file into iTunes and then sync with your iPhone.
Here are some more detailed instructions including screenshots;
Here are some more detailed instructions
Click on: Product - Archive (You must select IOS devices into active scheme and you not select IOS Simulator scheme).
When the run is terminated it's open the organizer view.
Right click on your app - Show in finder.
Right click on your archive into finder - Show package content - Products - Applications and here you find your file.app

App is misconfigured for Facebook Login in Android

I am writing an app in which i am allowing user to do login on fb, but whenever i am testing my app on mobile getting : App is misconfigured for Facebook Login
I don't know why i am getting this and how to resolve this issue?
I have generated hashkey and given in my Dashboard also, and i am also using App ID
but i don't know where i need to use App Secret in my app
Please help me ... to resolve this issue....
This is very major problem, while work with Facebook SDK and it means which keyhash you have generated that is wrong:
Please follow below steps:
Project (RightClick) > Android Tools > Export Signed Application Package
Export Android Application : Select Project > Next
Create New Keystore > Select Location to Save and give name as Project.keystore > Enter Password | Confirm Password
Key Creation- Enter Alias Name, password, Validity, Organisation Name > Next
Select path to save apk file, name it as Project.apk > Finish
Now follow below steps:
Download OpenSSL and save it into C:/
Copy all DLLs files from OpenSSL folder
Browse Java bin folder and paste these DLLs here along with keystore (Project.keystore)
Now open command prompt and follow this tutorial link:
www.helloandroid.com/tutorials/using-facebook-sdk-android-development-part-1

Can you create per-user project settings in Xcode?

I'm collaborating on an iPhone application, with the project files (.xcodeproj directory) checked into source control. One important setting is the "Code Signing Identity", which specifies the certificates to use to sign the application in order that it can run on the iPhone.
Each developer on the project has his own Code Signing Identity, so whenever anyone makes a change to the project, his Code Signing Identity gets saved into the project settings, and then everyone else inherits that change. They then have to change that to their CSI before they can continue.
Is there a way to have the Code Signing Identity saved in some local per-user project file that doesn't get checked into source control?
You could base the Xcode project on an .xcconfig file, then make each developer use their own .xcconfig file and keep the identity setting in there.
Either that or have your source control system ignore the file that contains the signature, in git you can create a file called .gitignore, theres probably a similar thing for what you are using. It means even though you've changed it the change won't get mirrored.
I worked around this by making different builds. The one named "Dev - Rob" had my settings in it, and the one named "Dev - [Other Guy's Name]" had Other Guy's settings.
We also used this to make builds like "Release - Beta" and "Release - AppStore" etc., for all situations where we'd have different signing configurations.