Skip to content
This repository has been archived by the owner on Sep 4, 2020. It is now read-only.

Please clarify the use of content-available in the payload doc #1679

Closed
ghost opened this issue Apr 12, 2017 · 4 comments
Closed

Please clarify the use of content-available in the payload doc #1679

ghost opened this issue Apr 12, 2017 · 4 comments
Labels

Comments

@ghost
Copy link

ghost commented Apr 12, 2017

I'm referring to issue #820 and #1577

@macdonst It might be helpful for all of us if you could clarify the required form of the content available property for both iOS and Android in the payload doc (https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md).

In the doc, there are actually two forms of the property content_available and content-available, so which is the right one? In the threads mentioned above yourself sometimes use one version or the other.

For the value of this property, there are "1", 1 and true, which is the correct one? Is there any different use expected for iOS and Android?

@macdonst macdonst added the docs label Apr 14, 2017
@fredgalvao
Copy link
Collaborator

https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#use-of-content-available-true

This part mentions content_available and content-available in a mixed fashion, we could use clarification there. The rest seems okay to me.

@iparrabb
Copy link

iparrabb commented Jul 7, 2017

I agree, the comunity needs a clear example of usage for Android and iOS, using FCM and APNS, I followed the examples of the payloads docs but is very difficult to get the expected result.

I have opened #1833 for this reason, I tested with FCM and APNS, works fine except on iOS but I have lost many hours of work for this reason.

@lock
Copy link

lock bot commented Jun 3, 2018

This thread has been automatically locked.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

3 participants