I'm generating Apple Wallet passes on a regular basis and I just got a message from Apple that my Pass Type ID certificate is about to be expired and I need to create a new one.
I know how to create a new certificate and start using it but I'm not sure what will happened to all the old passes I already created and are associated with the old certificate. I know they will still work on the users' devices but is there a way for me to keep pushing updates to these cards even though they were generated with the old certificate?
Just generate a new certificate associated with the passTypeIdentifier and use it to send pushes. It will work for all your passes, old and new.
Related
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.
I'm using this endpoint to subscribe for changes on a file: https://developers.google.com/drive/v3/reference/files/watch. While I'm receiving callbacks, some notifications don't happen right away and others seem to be dropped completely. I'm trying to figure out whether this is an issue with the service or something I'm not understanding about the API.
I've tried testing our setup with several different types of files and have gotten similar results with inconsistent notifications.
Wonder if anyone has done tests or has insider information about the reliability of change notifications? Is it around 99% or more like 50%? What is the expected distribution of delays? (it's definitely not instantaneous)
Without knowing what you have already done, I can only suggest that you check Push Notifications and see if you've missed some of the important things.
It was discussed that, to use push notifications, you need to do three things:
Register the domain of your receiving URL.
Set up your receiving URL, or "Webhook" callback receiver.
Set up a notification channel for each resource endpoint you want to watch.
In addition to that, note that there are required properties when making watch requests:
An id property string that uniquely identifies this new notification channel within your project. We recommend that you use a universally unique identifier (UUID) or any similar unique string.
A type property string set to the value web_hook.
An address property string set to the URL that listens and responds to notifications for this notification channel. This is your Webhook callback URL, and it must use HTTPS.
Also, Drive API will be able to send notifications to this HTTPS address only if there is a valid SSL certificate installed on your web server. Invalid certificates include:
Self-signed certificates.
Certificates signed by an untrusted source.
Certificates that have been revoked.
Certificates that have a subject that doesn't match the target hostname.
Hope that helps.
I'm working on generating some replacement APNs server certificates and I'm concerned because when I drag them into the keychain login they look different. Before the certificates looked like:
Apple Production IOS Push Services: com.mycompany.myproduct
But now they look like
Apple Production IOS Push Services: AB12C3DEF4;AB12C3DEF4
where "AB12C3DEF4" is the app prefix. Has anybody else seen this? If you've generated an APNs certificate lately, did it look like this?
This is the first time I've done this kind of generation since Apple changed their certificates interface...
I saw this also. It appears to be a bug; I filed a radar (also if you search you should see a post I created in the Apple Developer Forums).
In the meantime to make your certificates more findable, make sure to enter a unique name you want to search on in the "name" part of the "Request a certificate from a certificate authority" form that generates the request that creates the certificate. Whatever you enter in the name field will be what the private key is called, so search in keychain will still find your certificate and you'll be able to identify it from the private key name.
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