I uploaded app to Google Store and now when I want to publish new version I forgot/misplaced my password. So is there any chance to recover it or to reset it? I have done my app in Unity. And also did stupid thing, when setting the new password I run over my first user.keystore file. Any solutions to get the password out of this?
Thank you
I don't think it's possible to get the password out of a keystore. Keystores are encrypted security files. If you could get the password from the file, then that would mean that hackers could steal your key and use it. The fact that the key is overwritten does not make the situation any easier.
I hope you didn't already make your app publicly available on the play store. The only solution I could think of is to create a new app in the play store and an new key in unity.
If you enabled the new app signing by google play, it is possible to resubmit an app if you lost the key, see here:
Lost or compromised upload key?
If you’ve lost your private upload
key, or it’s been compromised, you can create a new one, and then ask
your account owner to contact support to reset the key. When
contacting support, make sure your account owner attaches the
upload_certificate.pem file.
After our support team registers the new upload key, you receive an email, and then you can update your keystores and register your key with API providers.
Important: Resetting your upload key doesn’t affect the app signing
key that Google Play uses to re-sign APKs before delivering them to
users.If you’ve lost your private upload
Here is the link for customer support by google.
Related
I commissioned a dev on upwork to build my app for me and release it into play store and app store, the agreenent was that I own the code but the dev has been using his own signing keys,etc.
Do I need to create my own signing keys to put into the code? Or do I need to be doing this myself?
Should I create my own Play account? Can I get my dev to release it into my play account?
What else do I need to replace to make it mine so I dont have to rely on that dev to make changes down the road?
Anything else I should worry about?
In order to be owner of your own code and be completely independent for future releases with another developer you would need the following:
Your own account on the App Store / Play Store, so you can manage developer's access when they do the release of the app, but you keep the account and full admin access and they can't temper with the app itself once released.
Git (github, gitlab, bitbucket or any 3rd party provider) account and repository to which you give access for the developer, so he can commit code of the app. This preserves the history of his work + you can manage multiple people having access on the same codebase. Also already pushed code can't be lost on his local PC.
Other than that all accounts that are needed for 3rd party services also need to be created by your own account. An example would be Firebase console account or google account to access it's API for geolocation or any other 3rd party...
Regarding keys...all keys that are generated during the development time serve for that development period, and they can be changed later on when new developer comes onboard. The developer can share them with you, so you too have access to it all, but that's not something that can block your action on the account/application at any point when you break up the contract for any reason.
You should own your apple and google store account and signing key for every app released on the stores.
Of course you have to own the code but if you want to publish your app the code needs to be built and get signing and be uploaded on the stores.
You could make your developer in charge in building, uploading and getting feedback from apple or goolge store team or customers
The signing key do nothing changes in your code. it will be used only when build your app and devlier to the stores and somewhere else.
I'm working on a large app. In the middle of development we decided to add push notifications. I created a new App ID in the Apple Developer Site.
The App ID is: 8NG823UBLP.com.mobiikk.ServicioDeAdministracionTributaria
Push is enabled for Production and Development.
Certificates were downloaded for both and the .p12 created too.
.p12 files are on the server and everything looks good on server side but the app is not receiving push notifications.
The app is granted push notifications and they are set to ON in settings.
The bundle ID was changed to com.mobiikk.ServicioDeAdministracionTributaria in the info.plist
The team has been looking for an answer for this without any luck. Help will be very much appreciated.
If you switch on notifications for existing app, you'll have to recreate the provisioning profile (better clear old profiles from Xcode organizer and then refresh them or shut down xcode and replace them via iphone configuration utility - be sure to get rid of older provisioning profiles)(you can still keep the same old appID, just refresh that AdHoc/Enterprise/AppStore profile - it contains note about being APNS-enabled)
Otherwise your serverside may look great, but app will never get successful notification of registering your device and could not pass token to your server side ,
but you would get failure notifications warning you about wrong entitlements and missing APNS profile in device console log
As you did not state what are you doing in the app side it's hard to tell where is your problem exactly.
Just in case someone has the same problem. The only way around this was to create a brand new project. I copied every file in the old one to the new one. Gave it a new Bundle ID, created a new provisioning profile, new App ID, and downloaded new certificates. So in summary, there was no easy way to transfer an existing project to one that accepted push notifications.
I hired an objective-c programmer to develop my iphone app, he wrote the code, and now I want to test the push notification service, but he wouldn't send me the p12 file, he said he cant send me the p12 key, because it contains his private key.
1) So can I create the p12 file myself, if so how can I do this? doesn't it need to be attached to the app? I need the app's id?
2) Can I just add him as a developer under my apple' developer account so he can set up everything?
The key used with APNS does not need to be the same key used for signing apps. It should not be the key used for signing apps, since it will end up installed on a virtual server on third-party hardware in a fourth-party data center. You might even want to use different development and production keys, if more people will have access to the development server (e.g. developers might run it on their own computers as necessary for debugging).
You can create the keypair, send him the CSR, get him to create the cert and send that to you, and use the cert on your server.
You'll need to set the app up under your own account at some point anyway (assuming you're not going to pay him to support it indefinitely) so you might as well do it now. Depending on how much you trust him, you can add him as a developer or just do it all yourself.
I'm pretty sure you can also give accounts restricted permissions - just enough to upload a CSR, create an "iPhone Development" cert, and download provisioning profiles. You can do the rest (add UDIDs, set up app IDs, and configure provisioning profiles), right?
You can create your own .p12 file and your app is not dependent on push notification certificate.
.P12 is used to authenticate and communicate between correct device and APNS server.
Check this tutorial
Once done you can test using by your own server if you have access or use the below tool to test
Pushtry.com
The company I work for has outsourced development of an iPhone app to another company. They want the binary to be signed with our certificate for distribution, but they've asked me to pass the private key (certificates.p12) used to create our certificate on to the other company. I am extremely concerned about handing the ability to sign applications as us over to another company.
How can I convince my boss this is a really bad idea? What alternative solutions can I suggest to him? I have already asked him to get the source from them so we can sign and submit it ourselves, but without the ability to conclusively state that giving them the certificate is a bad idea, I'm kinda stuck in the "just look into it for me" limbo.
You don't need the source. You just need the compiled binary (make sure it's ARM, not x86) to sign with codesign.
The outsource company can just build and sign the app with their own certificate. You can then resign the app with your company's certificate before submission (use codesign).
There's not too much a consultant can do with the private key to just an App store Distribution certificate but without the team agent's iTunes Connect login credentials, as Apple's review team are the only ones who can run an app signed with your Distribution certificate, and you can't submit an app to iTunes Connect without the login matching the certificate (AFAIK).
I am finishing an app for my client.
He wants to submit it to Apple himself.
What must I do ?
Should I give him the app unsigned ?
Should I ask him a provisioning profile ?
Should I be added to his team and to his Distribution Profile ?
Thanks a lot for your help ?
Thierry
Have your client sign up for the iPhone Developer Program so that way when your client submits the app to the App Store it will be under the client's company name. You can still manage all the code signing and provisioning for your client if they do not know how to do this stuff. The client can simply give u access to their developer account to handle all that stuff.
I would just give him the source code, unless you specifically don't want to do that for some reason. That way, he can just compile it himself.
What I've done for clients who want to submit to Apple themselves:
The client must create (or you can create for them if they give you their login info) the app store distribution profile for the app and send it to you. Requires some communication between you and client to make sure they use the right app id, etc.
(I think you may need the client's developer certificate as well in order for them to "own" the app -- not 100% sure about this)
Don't forget to also get the private key file as the certificate signing won't work without it
I set the client cert / app store dist profile into the app and build the app for app store.
Deliver the binary to the client.
Client uploads to itunes connect.