'Incorrect padding' on APNS notification request about sygnal HOT 14 CLOSED

Plainly, your device token seems to be wrong.

Oddly, I get a different error to you:

>>> pk = "APA91bHPRgkF3JUikC4ENAHEeMrd41Zxv3hVZjC9KtT8OvPVGJ-hQMRKRrZuJAEcl7B338qju59zJMjw2DELjzEvxwYv7hH5Ynpc1ODQ0aT4U4OFEeco8ohsN5PjL1iC2dNtk2BAokeMCg2ZXKqpc8FXKmhX94kIxQ"                                                                

>>> base64.b64decode(pk)                                                                                                                                                                                                                     
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.7/base64.py", line 87, in b64decode
    return binascii.a2b_base64(s)
binascii.Error: Invalid base64-encoded string: number of data characters (161) cannot be 1 more than a multiple of 4

Invalid base64-encoded string: number of data characters (161) cannot be 1 more than a multiple of 4

Without knowing specifics about how you're getting your device tokens, it's hard to offer any advice.

Something is going wrong with your base64 encoding...

from sygnal.

are you sending it to Sygnal as a string or encoded?

from sygnal.

@myoussef89 the above pk is 'fcmToken' srting that i got from Firebase ,and i send it as a string not b64decode.

from sygnal.

I'm afraid I'm rather confused, are you two related in some way?

@myoussef89 the above pk is 'fcmToken' srting that i got from Firebase ,and i send it as a string not b64decode.

Firebase FCM (once known as GCM, typically used for Android) and APNs (used for iOS) are two different systems.

If you give Sygnal a FCM token, it needs to be for a FCM app ID.

i.e. "app_id": "com.xxxxxxxxxx:xxxxxxxxxx.matrix", then com.xxxxxxxxxx:xxxxxxxxxx.matrix in your config needs to refer to a GCM/FCM-type app.

from sygnal.

yes, we are working together on the same project.

Does that mean IOS is only working with APNS, Not supported on firebase ?

from sygnal.

You are using iOS with FCM?

from sygnal.

we tried to use it for FCM because we are having trouble receiving notification with APNS. before IOS 13.3 it was working after Apple's last updates we are not receiving VOIP notifications or text notifications anymore.

from sygnal.

OK so my understanding is:

• When you use FCM on iOS, FCM will talk to APNs on your behalf.
  • so you should not configure Sygnal with APNs
  • You need to give your APNs credentials to FCM
  • then you can try configuring Sygnal to use FCM (GCM) for your iOS app
    • I don't know if anyone has tried this, but after skimming FCM's documentation, it seems like it stands a chance

I don't know if going through FCM will help your problem, though.

from sygnal.

yes, that exactly what we are trying to do.

from sygnal.

Your error message indicates that Sygnal is configured with type: apns when it needs to be type: gcm if you are using FCM.

from sygnal.

Your error message indicates that Sygnal is configured with type: apns when it needs to be type: gcm if you are using FCM.

yes, I think we messed up the tokens when we were trying on APNS.

from sygnal.

Is this now resolved? :)

from sygnal.

Is this now resolved? :)

I think for the current error yes

from sygnal.

how did you finally resolve it ?, can you share the structure of your sygnal.yaml ? i seem to have the same problem

from sygnal.