I followed the FCM docs and noticed that the device_token param passed to the invalid_config proc is a string and not an object, which raised a NoMethod error in my proj when calling destroy on it.
Description:
Updated the docs to match the expected behavior
Testing:
N/A
Checklist:
[ ] Code follows the project's coding standards
[ ] Tests have been added or updated to cover the changes
[X] Documentation has been updated (if applicable)
[ ] All existing tests pass
[ ] Conforms to the contributing guidelines
Additional Notes:
I might be missing sth, but the device_tokens config plucks the token out of the NotificationToken obj, so I don't think it was specific to my implementation the fact that the invalid_config proc takes a string instead of an obj
Pull Request
device_tokenparam passed to theinvalid_configproc is a string and not an object, which raised aNoMethoderror in my proj when callingdestroyon it.Description:
Testing: N/A
Checklist:
Additional Notes:
device_tokensconfig plucks the token out of theNotificationTokenobj, so I don't think it was specific to my implementation the fact that theinvalid_configproc takes a string instead of an obj