marcick Well-Known Member Licensed User Longtime User Apr 6, 2020 #1 Hi guys, I just want a confirmation that these steps are correct when APN certificate is about to expire From Apple developer console generate the new APN certrificate aps.cer and copy it in B4i keys folder in B4i Keys folder, leave only the new aps.cer (move to other folders other existing .cer like IOS_Distribution) From B4i IDE, Tool-Build server-Create push keystore (Firebase service). A new firebase_push.p12 file is generated Move to "cloud messaging section" in Firebase console Update the .p12 file, using the B4i Private sign Key as password From B4i IDE, Tool-Build server-Create push keystore (B4X push server). A new Push.Keystore file is generated. Move to the B4J app that need to generate notifications and copy in its folder the new Push.Keystore restore back the IOS_Distribution.cer in the B4i keys folder From Apple developer console, revoke the certificate expiring Correct ?
Hi guys, I just want a confirmation that these steps are correct when APN certificate is about to expire From Apple developer console generate the new APN certrificate aps.cer and copy it in B4i keys folder in B4i Keys folder, leave only the new aps.cer (move to other folders other existing .cer like IOS_Distribution) From B4i IDE, Tool-Build server-Create push keystore (Firebase service). A new firebase_push.p12 file is generated Move to "cloud messaging section" in Firebase console Update the .p12 file, using the B4i Private sign Key as password From B4i IDE, Tool-Build server-Create push keystore (B4X push server). A new Push.Keystore file is generated. Move to the B4J app that need to generate notifications and copy in its folder the new Push.Keystore restore back the IOS_Distribution.cer in the B4i keys folder From Apple developer console, revoke the certificate expiring Correct ?
marcick Well-Known Member Licensed User Longtime User Apr 6, 2020 #2 uhmmm ... perhaps push.keystore was needed only for the old GCM notification as in no longer required with Firebase ? Upvote 0
uhmmm ... perhaps push.keystore was needed only for the old GCM notification as in no longer required with Firebase ?
Erel B4X founder Staff member Licensed User Longtime User Apr 6, 2020 #3 2. not needed. 5 - 8. not needed Upvote 0
marcick Well-Known Member Licensed User Longtime User Apr 6, 2020 #4 About 2: I remember in the past there were errors if multiple .cer were present in the keys folder, I see now is ok, thanks. About 5: The Firebase console also inform the certificate is expiring, why you say this step is not needed ? About 6-8: ok Upvote 0
About 2: I remember in the past there were errors if multiple .cer were present in the keys folder, I see now is ok, thanks. About 5: The Firebase console also inform the certificate is expiring, why you say this step is not needed ? About 6-8: ok
Erel B4X founder Staff member Licensed User Longtime User Apr 6, 2020 #5 You are correct. I thought that you meant to something else. Note that you can also use the new key format with Firebase. I don't remember the exact terms however you just need to download the new type of key and upload it to Firebase. Upvote 0
You are correct. I thought that you meant to something else. Note that you can also use the new key format with Firebase. I don't remember the exact terms however you just need to download the new type of key and upload it to Firebase.
Erel B4X founder Staff member Licensed User Longtime User Aug 10, 2020 #6 Not needed (though it is worth testing it after the change). Upvote 0
