iOS Question Steps with FirebaseNotifications after new provision files

[Cadenzo]

This could be a stupid question. But when starting with B4i, I just followed any step in the tutorials with this certificates and provision files and than with integrating also FirebaseNotifications. I was lucky that everything worked, but without total understanding how.

Now, after one year I had to renew as normaly my apple developer account and created new mobileprovision files. Fine, but which steps I have to repeat now in this tutorial for the firebase integration? This files like firebase_push.p12? My app workes, but the firebase messages seems not to arrive now.

 

[Semen Matusovskiy]

Could be different reasons. What did you do with APS certificate ?

B4I obviously uses aps.cer to create firebase_push.p12. So, if aps.cer is new, then firebase_push.p12 is changed.
Meanwhile firebase_push.p12 is used for APNS certificates in Firebase Console.

One year is a big period. I'd download current Googleservice-info.plist in Firebase Console, and also replaced a key of server. And, of course, I'd replace APNs certificates.

 

[Cadenzo]

Thanks for response. Now I tried many things. APS certificate was still valid, but I created a new, to be sure. Downloaded aps.cer, created in IDE firebase_push.p12, uploaded it to firebase console, downloaded the GoogleService-Info.plist to special folder. No success.

Than I saw, that I have two Apple Push Services in Apple Certificats. The old and the new one. So I revoked booth and created a new. Of Course repeating all this funny file exchanges (up-downloads) - No success.

Than I saw, that my profiles (Ad hoc and App Store) are not valid any more. Guess, because I revoked the APS Certificates. So with "Edit" I could renew this certificates and download it. App shows no errors, but I can not receive this firebase messages, what ever I try. What else can I do?

This is the log:

Application_Start
Application_Active
FCMConnected
GetToken: ...
Application_Pushtoken
PushToken: 1
<B4IExceptionWrapper: (null)>
Class (b4i_httpjob) instance released.

 

[Cadenzo]

This is the Keys-folder. So after aps.cer and firebase_push.p12 I renewed also the mobileprovision files for this App. Is that so OK, did I forget something? Also I renewed the GoogleService-Info.plist in the "Special" folder.

 

[Cadenzo]

And this are the types of Certificates and Profiles on the Apple account...

 

[Semen Matusovskiy]

Did you change APNS certificates in Firebase Console ?

You can try to send messages using Erel's SendingTool https://www.b4x.com/android/forum/attachments/sendingtool-zip.45776/.

But don't forget to change API_KEY (take a look current key in Firebase Console) and a group of topics.

 

[Cadenzo]

What are the APNS certificates? Following the tutorials I have just to upload the firebase_push.p12 file to Firebase Console. This I did.
I did not upload a *.p8 file (authentification, because I dont have such file) only this p12, created from the B4i IDE. Is that correct?

I have also a working sending tool to test with. It works perfect for Android and it worked already with my iOS version. So the sending part should not be the problem.

 

[Semen Matusovskiy]

APNs: Settings, Cloud messaging

Note there are two fields - one for development certificate, another - for distribution

Well, hard to imaging what's wrong.

Did you look your App Id in Apple Console. Should be:

 

[Cadenzo]

Yes, this steps are done and OK. It looks like your screenshot.

 

[Semen Matusovskiy]

If settings in Apple and Firebase consoles are correct, remains the last - to check API-KEY and a notification format (Android and IOS formats are different).
I'd check Erel's SendingTools. At least, it will be visible what returns fcm.googleapis.com/fcm/send

 

[Cadenzo]

It works!!! Hard to say, what the reason was. I started now from zero with all this files on the apple account and it is working.

Thank you a lot for your support!!!