DeliveryPoint=Unknown

314 views
Skip to first unread message

f.pia...@gmail.com

unread,
Mar 25, 2013, 7:46:47 AM3/25/13
to uni...@googlegroups.com
Hi Monnand,
I'm tryng to send push to my smartphone, but the uniqush log now is saying that DeliveryPoint is Unknown .
Pheraps is something wrong in my configuration ?

I send you my log:

curl http://127.0.0.1:9898/push -d service=PushParking -d subscriber=fabrizio.client -d msg="Hello World"
[Push][Info] 2013/03/25 12:39:54 RequestId=cb8b9c91-bd08-47a6-4144-55a2ea4d6d7c From=127.0.0.1:60602 Service=PushParking Subscribers="[fabrizio.client]"
[Push][Info] 2013/03/25 12:39:54 RequestID=cb8b9c91-bd08-47a6-4144-55a2ea4d6d7c Service=PushParking Subscriber= PushServiceProvider=gcm:e94fd6cb3390be4dd68e89df18a7c6d5fe0c71b0 DeliveryPoint=Unknown Failed: BadPushServiceProvider gcm:e94fd6cb3390be4dd68e89df18a7c6d5fe0c71b0

Thank you .
Fabrizio


Monnand

unread,
Mar 25, 2013, 12:17:18 PM3/25/13
to uni...@googlegroups.com
Now I see the problem.

The DeliveryPoint=unknown is not the key point. The reason is:
BadPushServiceProvider.

This is because GCM returned an HTTP response with status code 401.

According to google( http://developer.android.com/google/gcm/gcm.html ),
it means: "There was an error authenticating the sender account."

In another word, the API key you provide may be invalid and cannot be
recognized by google.

You may want to test your API key against the following command to see
if it is correct:

curl --header "Authorization: key=$APIKEY" --header
Content-Type:"application/json" https://android.googleapis.com/gcm/send
-d "{\"registration_ids\":[\"$REGID\"]}"

replace the $APIKEY and $REGID with your API key and registration ID
respectively. (you may want to set variables named APIKEY and REGID in
your shell session instead, so that you can directly copy&paste the
command above)

Here is what I got on my machine:

monnand@~/$ APIKEY=YOUR_API_KEY
monnand@~/$ REGID=YOUR_REG_ID
monnand@~/$ curl --header "Authorization: key=$APIKEY" --header
Content-Type:"application/json" https://android.googleapis.com/gcm/send
-d "{\"registration_ids\":[\"$REGID\"]}"

The command above will let you communicate with GCM directly. If it
returns 401, then it means your API Key is invalid. You may want to
check it and try again.

Regards,
-Nan
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "uniqush" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to uniqush+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Monnand

unread,
Mar 25, 2013, 12:21:24 PM3/25/13
to uni...@googlegroups.com
FYI,

Here is how a google engineer's suggestion on how to debug with GCM.
similar as what I said.

https://plus.google.com/u/0/104524825852741167674/posts/cVqvTuoARCU

On 03/25/2013 07:46 AM, f.pia...@gmail.com wrote:

Fabrizio Piantone

unread,
Mar 25, 2013, 2:10:45 PM3/25/13
to uni...@googlegroups.com
VERY GOOD !
I will follow your precious instructions.
:-)

Fabrizio



2013/3/25 Monnand <mon...@gmail.com>

For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to a topic in the Google Groups "uniqush" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/uniqush/8Co-xZrIb7U/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to uniqush+unsubscribe@googlegroups.com.

Fabrizio Piantone

unread,
Mar 26, 2013, 2:36:58 PM3/26/13
to uni...@googlegroups.com
Hi Monnand,
i did some attempts and i have followed your instructions, but the results is always:


<HTML>
<HEAD>
<TITLE>Unauthorized</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Unauthorized</H1>
<H2>Error 401</H2>
</BODY>
</HTML>

As a proof to see if my APIKEY is correct i tried more and more times with another Push Server ("Zend_Mobile_Push - Mike Willbanks":http://framework.zend.com/wiki/display/ZFPROP/Zend_Mobile_Push+-+Mike+Willbanks) and the result is that I'm able to send and receive push with it.

Just to say that I do not think that the authentication problem is derived by the wrong APIKEY.

Could it be another parameter I'm Using ?

I describe you the steps I Have Followed in my proofs:

1- Set Variable $APIKEY: APIKEY=<string>
2- Collect $REGID with GCM DEMO PUSH APP: REGID=<string>
3- Set Variable $REGID: REGID=<string>
3- ADD-SP: curl http://127.0.0.1:9898/addpsp -d service=Opera21Push -d pushservicetype="gcm" -d projectid=893903042662 -d apikey=$APIKEY
4- SUBSCRIBE USER: curl http://127.0.0.1:9898/subscribe -d service=Opera21Push -d subscriber=fabrizio.client -d pushservicetype=gcm -d regid=$REGID
5- SEND PUSH: curl http://127.0.0.1:9898/push -d service=Opera21Push -d subscriber=fabrizio.client -d msg="Hello World"

RESULT:
[Push][Info] 2013/03/26 19:19:12 RequestID=b7f4902f-016b-4dc5-7c75-bdee3a9ac394 Service=Opera21Push Subscriber= PushServiceProvider=gcm:209b05a9271ce245efdcb6cc5af2f65fb71dc600 DeliveryPoint=Unknown Failed: BadPushServiceProvider gcm:209b05a9271ce245efdcb6cc5af2f65fb71dc600


I follow another session with the Zend_Mobile_Push and the user subscribe on gcm and receive messages from my php page without problems.... that's very strange!! 

I think that could be something wrong i do in calling your UNIQUSH Server, but i can't understand what !

Do you have some idea ?

Thanks a lot.
:-)
Fabrizio








2013/3/25 Monnand <mon...@gmail.com>
On 03/25/2013 07:46 AM, f.pia...@gmail.com wrote:

For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to a topic in the Google Groups "uniqush" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/uniqush/8Co-xZrIb7U/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to uniqush+unsubscribe@googlegroups.com.

Monnand

unread,
Mar 26, 2013, 9:41:56 PM3/26/13
to uni...@googlegroups.com
Now I see the problem.

See replies below:

On 03/26/2013 02:36 PM, Fabrizio Piantone wrote:
> Hi Monnand,
> i did some attempts and i have followed your instructions, but the
> results is always:
>
>
> <HTML>
> <HEAD>
> <TITLE>Unauthorized</TITLE>
> </HEAD>
> <BODY BGCOLOR="#FFFFFF" TEXT="#000000">
> <H1>Unauthorized</H1>
> <H2>Error 401</H2>
> </BODY>
> </HTML>
>

If the reply from google is 401, then it means your API key is invalid.
So what happened then? Let's move on.

> As a proof to see if my APIKEY is correct i tried more and more times
> with another Push Server ("Zend_Mobile_Push - Mike
> Willbanks":http://framework.zend.com/wiki/display/ZFPROP/Zend_Mobile_Push+-+Mike+Willbanks)
> and the result is that I'm able to send and receive push with it.
>

I just took a look at the Zend Mobile Push and saw the problem:

It supports the following platforms:

Windows Phone
Apple Push Notification Service
Android Cloud to Device Messaging

Notice that they are using C2DM (Cloud to Device Messaging) not GCM
(Google Cloud Massaging). In fact, Zend does not support GCM. That's why
both uniqush and google cannot accept your API Key.

C2DM is supported by uniqush as well, but I highly recommend not to use
it, because it was officially deprecated by google.

See the notice from C2DM's main page:

"Important: C2DM has been officially deprecated as of June 26, 2012.
This means that C2DM has stopped accepting new users and quota requests.
No new features will be added to C2DM. However, apps using C2DM will
continue to work. Existing C2DM developers are encouraged to migrate to
the new version of C2DM, called Google Cloud Messaging for Android
(GCM). See the C2DM-to-GCM Migration document for more information.
Developers must use GCM for new development. "

1. If you are using code for C2DM, you may want to migrate to GCM, which
is quite simple. See this document:
http://developer.android.com/google/gcm/c2dm.html

2. Since it is a transition time now, google supports both C2DM and GCM.
That's probably why you can still use C2DM to register a new device.

3. To get a valid API KEY, check out this document:
http://developer.android.com/google/gcm/gs.html

The procedure below has no problem as long as you have the right APIKEY
and REGID. I can successfully push notification from my machine, so I
think you can do it as well.

Please let me know your progress and I will be willing to provide help.

Regards,
-Monnand

P.S. One critique to Zend Mobile Push: you may not want to put your
password directly in the source code, which is highly dangers. But this
is what Zend asked developers to do. Technically, it is not safe and I
may not want to go that way.
> 2013/3/25 Monnand <mon...@gmail.com <mailto:mon...@gmail.com>>
>
> On 03/25/2013 07:46 AM, f.pia...@gmail.com
> <mailto:f.pia...@gmail.com> wrote:
>
> Hi Monnand,
> I'm tryng to send push to my smartphone, but the uniqush log now is
> saying that DeliveryPoint is Unknown .
> Pheraps is something wrong in my configuration ?
>
> I send you my log:
>
> curl http://127.0.0.1:9898/push -d service=PushParking -d
> subscriber=fabrizio.client -d msg="Hello World"
> [Push][Info] 2013/03/25 12:39:54
> RequestId=cb8b9c91-bd08-47a6-__4144-55a2ea4d6d7c
> From=127.0.0.1:60602 <http://127.0.0.1:60602>
> Service=PushParking Subscribers="[fabrizio.client]__"
> [Push][Info] 2013/03/25 12:39:54
> RequestID=cb8b9c91-bd08-47a6-__4144-55a2ea4d6d7c Service=PushParking
> Subscriber=
> PushServiceProvider=gcm:__e94fd6cb3390be4dd68e89df18a7c6__d5fe0c71b0
> DeliveryPoint=Unknown Failed: BadPushServiceProvider
> gcm:__e94fd6cb3390be4dd68e89df18a7c6__d5fe0c71b0
>
> Thank you .
> Fabrizio
>
>
>
> Now I see the problem.
>
> The DeliveryPoint=unknown is not the key point. The reason is:
> BadPushServiceProvider.
>
> This is because GCM returned an HTTP response with status code 401.
>
> According to google(
> http://developer.android.com/__google/gcm/gcm.html
> <http://developer.android.com/google/gcm/gcm.html> ), it means:
> "There was an error authenticating the sender account."
>
> In another word, the API key you provide may be invalid and cannot
> be recognized by google.
>
> You may want to test your API key against the following command to
> see if it is correct:
>
> curl --header "Authorization: key=$APIKEY" --header
> Content-Type:"application/__json"
> https://android.googleapis.__com/gcm/send
> <https://android.googleapis.com/gcm/send> -d
> "{\"registration_ids\":[\"$__REGID\"]}"
>
> replace the $APIKEY and $REGID with your API key and registration ID
> respectively. (you may want to set variables named APIKEY and REGID
> in your shell session instead, so that you can directly copy&paste
> the command above)
>
> Here is what I got on my machine:
>
> monnand@~/$ APIKEY=YOUR_API_KEY
> monnand@~/$ REGID=YOUR_REG_ID
> monnand@~/$ curl --header "Authorization: key=$APIKEY" --header
> Content-Type:"application/__json"
> https://android.googleapis.__com/gcm/send
> <https://android.googleapis.com/gcm/send> -d
> "{\"registration_ids\":[\"$__REGID\"]}"
>
> The command above will let you communicate with GCM directly. If it
> returns 401, then it means your API Key is invalid. You may want to
> check it and try again.
>
> Regards,
> -Nan
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "uniqush" group.
> To unsubscribe from this group and stop receiving emails from
> it, send
> an email to uniqush+unsubscribe@__googlegroups.com
> <mailto:uniqush%2Bunsu...@googlegroups.com>.
> For more options, visit
> https://groups.google.com/__groups/opt_out
> <https://groups.google.com/groups/opt_out>.
>
>
>
> --
> You received this message because you are subscribed to a topic in
> the Google Groups "uniqush" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/__topic/uniqush/8Co-xZrIb7U/__unsubscribe?hl=en
> <https://groups.google.com/d/topic/uniqush/8Co-xZrIb7U/unsubscribe?hl=en>.
> To unsubscribe from this group and all its topics, send an email to
> uniqush+unsubscribe@__googlegroups.com
> <mailto:uniqush%2Bunsu...@googlegroups.com>.
> For more options, visit https://groups.google.com/__groups/opt_out
> <https://groups.google.com/groups/opt_out>.
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "uniqush" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to uniqush+u...@googlegroups.com.

Fabrizio Piantone

unread,
Mar 27, 2013, 5:44:53 AM3/27/13
to uni...@googlegroups.com
Hi monnand I thank you for your explanation, I know that your approach , for authentication is better, because you don't have to use credentials to AAA , but I'm just using GCM. I have just followed the instructions (http://developer.android.com/google/gcm/gs.html) since 3 months ago and using a project that is supporting GCM called Zend_Mobile (look here : https://github.com/mwillbanks/Zend_Mobile/blob/master/README.textile )

This component (Zend_Mobile) allows you to send push notifications with Zend Framework. This library currently supports:

  • APNS: Apple Push Notification Service (iTouch/iPad/iPhone)
  • GCM: Google Cloud Messaging (Android – Google)
  • MPNS: Microsoft Push Notification Service (Windows Mobile)

.............

So I just used Google procedure to create a server GCM APIKEY , as I told you. I think that the problema instead, could be in my Uniqush configuration, due to i would ask you an example of your Uniqush-push.conf configuration file just to compare with mine:

logfile=/var/log/uniqush
# Log level: verbose, standard,
[WebFrontend]
log=on
loglevel=standard
addr=localhost:9898

[AddPushServiceProvider]
log=on
loglevel=standard

[RemovePushServiceProvider]
log=on
loglevel=standard

[Subscribe]
log=on
loglevel=standard

[Unsubscribe]
log=on
loglevel=standard

[Push]
log=on
loglevel=standard

[Database]
engine=redis
port=6379
name=0
everysec=600
leastdirty=10
cachesize=1024











2013/3/27 Monnand <mon...@gmail.com>

        For more options, visit
        https://groups.google.com/__groups/opt_out
        <https://groups.google.com/groups/opt_out>.



    --
    You received this message because you are subscribed to a topic in
    the Google Groups "uniqush" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/__topic/uniqush/8Co-xZrIb7U/__unsubscribe?hl=en
    <https://groups.google.com/d/topic/uniqush/8Co-xZrIb7U/unsubscribe?hl=en>.
    To unsubscribe from this group and all its topics, send an email to
    uniqush+unsubscribe@__googlegroups.com

--
You received this message because you are subscribed to the Google
Groups "uniqush" group.
To unsubscribe from this group and stop receiving emails from it, send

For more options, visit https://groups.google.com/groups/opt_out.


--
You received this message because you are subscribed to a topic in the Google Groups "uniqush" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/uniqush/8Co-xZrIb7U/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to uniqush+unsubscribe@googlegroups.com.

Monnand

unread,
Mar 30, 2013, 3:15:00 PM3/30/13
to uni...@googlegroups.com
On 03/27/2013 05:44 AM, Fabrizio Piantone wrote:
> This component (Zend_Mobile) allows you to send push notifications with
> Zend Framework. This library currently supports:
>
> * APNS: Apple Push Notification Service (iTouch/iPad/iPhone)
> * GCM: Google Cloud Messaging (Android – Google)
> * MPNS: Microsoft Push Notification Service (Windows Mobile)
>

Well... I read an out-of-date document saying it does not support GCM.
That's fine.
> .............
>
> So I just used Google procedure to create a server GCM APIKEY , as I
> told you. I think that the problema instead, could be in my Uniqush
> configuration, due to i would ask you an example of your
> Uniqush-push.conf configuration file just to compare with mine:
>

I have exactly the same configuration file as yours. It is very unlikely
to be the configuration's problem because you can hardly change any
information about a provider inside the config file.

Did you say that even if you connect google directly using curl, you
still got same 401 error?

Here is the procedure of testing your APIKEY. The procedure below is
from google's official document, so it is definitely a reliable method:

``
You can check the validity of your API key by running the following command:

# api_key=YOUR_API_KEY
# curl --header "Authorization: key=$api_key" --header
Content-Type:"application/json" https://android.googleapis.com/gcm/send
-d "{\"registration_ids\":[\"ABC\"]}"

If you receive a 401 HTTP status code, your API key is not valid.
Otherwise you should see something like this:

{"multicast_id":6782339717028231855,"success":0,"failure":1,"canonical_ids":0,"results":[{"error":"InvalidRegistration"}]}
''

See this: http://developer.android.com/google/gcm/gcm.html#auth_error

Fabrizio Piantone

unread,
Apr 1, 2013, 11:13:09 AM4/1/13
to uniqush
Hi Monnand, I'm sorry but in Europe we have Easter Holydays so i couln't answer your mail till now.
So I followed you latest instructions but the problem is still there. Now i think the problem could be in the system architecture and network ...
In the actual implementation of Uniqush i have installed it in a private LAN so it is not reacheable from the internet, but it can contact the internet. I should try to change this configuration so i can do the same tests i did successfully with ZEND_mobile GCM that is placed on a server with public IP. As another idea i could think is to configure an apache server to proxy Uniqush POSTs ....
I think this is the last chanche i have to try to use Uniqush... :-)

thanx a lot
fabrizio




2013/3/30 Monnand <mon...@gmail.com>

Fabrizio Piantone

unread,
Apr 1, 2013, 12:22:01 PM4/1/13
to uniqush
Hi Monnand,
now it's ok !!
I can send and receive push messages on smartphones . The problem was as i thought, a stupid problem in the network configuration , so after i moved the uniqush server on another server with natted IPs and the problem i solved now.
My GCM API keys were correct and the Zend_mobile application too.
Now i will try your uniqush and i will ask you other questions in another thread.
Did you released the package 1.4.2 or you are waiting to test it ?
Thanks again,
Fabrizio


2013/4/1 Fabrizio Piantone <f.pia...@gmail.com>

Monnand

unread,
Apr 1, 2013, 1:56:11 PM4/1/13
to uni...@googlegroups.com
On 04/01/2013 12:22 PM, Fabrizio Piantone wrote:
> Hi Monnand,
> now it's ok !!

Great! I'm so glad to hear that.

> I can send and receive push messages on smartphones . The problem was as
> i thought, a stupid problem in the network configuration , so after i
> moved the uniqush server on another server with natted IPs and the
> problem i solved now.

Now I see. This is interesting. I should take a note on this for further
reference.

> My GCM API keys were correct and the Zend_mobile application too.
> Now i will try your uniqush and i will ask you other questions in
> another thread.
> Did you released the package 1.4.2 or you are waiting to test it ?

I am going to release it now. (May be one or two hours later)

-Monnand
> Thanks again,
> Fabrizio
>
>
> 2013/4/1 Fabrizio Piantone <f.pia...@gmail.com
> <mailto:f.pia...@gmail.com>>
>
> Hi Monnand, I'm sorry but in Europe we have Easter Holydays so i
> couln't answer your mail till now.
> So I followed you latest instructions but the problem is still
> there. Now i think the problem could be in the system architecture
> and network ...
> In the actual implementation of Uniqush i have installed it in a
> private LAN so it is not reacheable from the internet, but it can
> contact the internet. I should try to change this configuration so i
> can do the same tests i did successfully with ZEND_mobile GCM that
> is placed on a server with public IP. As another idea i could think
> is to configure an apache server to proxy Uniqush POSTs ....
> I think this is the last chanche i have to try to use Uniqush... :-)
>
> thanx a lot
> fabrizio
>
>
>
>
> 2013/3/30 Monnand <mon...@gmail.com <mailto:mon...@gmail.com>>
> Content-Type:"application/__json"
> https://android.googleapis.__com/gcm/send
> <https://android.googleapis.com/gcm/send> -d
> "{\"registration_ids\":[\"ABC\__"]}"
>
> If you receive a 401 HTTP status code, your API key is not
> valid. Otherwise you should see something like this:
>
> {"multicast_id":__6782339717028231855,"success":__0,"failure":1,"canonical_ids":__0,"results":[{"error":"__InvalidRegistration"}]}
> ''
>
> See this:
> http://developer.android.com/__google/gcm/gcm.html#auth_error
> https://groups.google.com/d/__topic/uniqush/8Co-xZrIb7U/__unsubscribe?hl=en
> <https://groups.google.com/d/topic/uniqush/8Co-xZrIb7U/unsubscribe?hl=en>.
> To unsubscribe from this group and all its topics, send an email
> to uniqush+unsubscribe@__googlegroups.com
> <mailto:uniqush%2Bunsu...@googlegroups.com>.
> For more options, visit
> https://groups.google.com/__groups/opt_out
> <https://groups.google.com/groups/opt_out>.
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "uniqush" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to uniqush+u...@googlegroups.com.

vinu saju

unread,
Sep 30, 2014, 3:08:34 AM9/30/14
to uni...@googlegroups.com
I'm trying to send push to my smartphone, but the uniqush log now is saying that Delivery Point is Unknown .
Please find attached logs.

vs571025@01hwxxxxxx:~$ curl http://127.0.0.1:9898/push -d service=myservice -d subscriber=uniqush.client -d msg="Hello"
[Push][Info] 2014/09/29 12:25:07 RequestId=5429024b-F9xOMyuRd04mHhxiygn04A== From=127.0.0.1:47829 Service=myservice Subscribers="[uniqush.client]"
[Push][Error] 2014/09/29 12:25:08 RequestID=5429024b-F9xOMyuRd04mHhxiygn04A== Service=myservice Subscriber= PushServiceProvider=gcm:e38903bdea71d7f39edb3b7accfde48029f80d31 DeliveryPoint=Unknown Failed: BadPushServiceProvider gcm:e38903bdea71d7f39edb3b7accfde48029f80d31
[Push][Error] 2014/09/29 12:25:08 RequestID=5429024b-F9xOMyuRd04mHhxiygn04A== Service=myservice Subscriber= PushServiceProvider=gcm:b0619c181f83d08acf472e5490af0d505999f0ca DeliveryPoint=Unknown Failed: BadPushServiceProvider gcm:b0619c181f83d08acf472e5490af0d505999f0ca

Am trying to run below commands also.

vs571025@01hwxxxxxx:~$ APIKEY=AIzaSyBpT_plPSyQf9NX4pD2yA7eJjujqtyLXXo
vs571025@01hwxxxxxx:~$REGID=APA91bG5gX-Oqxhe5nCGJbKhF9-pcvqmQq3-O8kV7kNET6NXo7g61Er2OxnxQKOcRhvnY5Vf5v1vPtv50KhOWyLIfmL2sSNbwkpljJrxVQpvxeQ0dEXAmUmQ36uvaFdSoZuVBbAuP1-UiA8VmuJNqI4EyV_W3TuyGUVzg1UeP_FtqBeSLo0F4NMREGID=APA91bG5gX-Oqxhe5nCGJbKhF9-pcvqmQq3-O8kV7kNET6NXo7g61Er2OxnxQKOcRhvnY5Vf5v1vPtv50KhOWyLIfmL2sSNbwkpljJrxVQpvxeQ0dEXAmUmQ36uvaFdSoZuVBbAuP1-UiA8VmuJNqI4EyV_W3TuyGUVzg1UeP_FtqBeSLo0F4NM
vs571025@01hwxxxxxx:~$ curl --header "Authorization: key=AIzaSyBpT_plPSyQf9NX4pD2yA7eJjujqtyLXXo" --header Content-Type:"application/json" https://android.googleapis.com/gcm/send -d "{\"registration_ids\":[\"APA91bG5gX-Oqxhe5nCGJbKhF9-pcvqmQq3-O8kV7kNET6NXo7g61Er2OxnxQKOcRhvnY5Vf5v1vPtv50KhOWyLIfmL2sSNbwkpljJrxVQpvxeQ0dEXAmUmQ36uvaFdSoZuVBbAuP1-UiA8VmuJNqI4EyV_W3TuyGUVzg1UeP_FtqBeSLo0F4N"]}"


2013/4/1 Fabrizio Piantone <f.pia...@gmail.com>


2013/3/30 Monnand <mon...@gmail.com>
To unsubscribe from this group and all its topics, send an email to uniqush+u...@googlegroups.com.

dev....@gmail.com

unread,
Jul 12, 2017, 6:30:43 AM7/12/17
to uniqush
Yeah. Need to takecare while you adding APIKEY, its not APP KEY, when I used "Legacy server key" under Cloud Messaging.
Its worked.

Thanks for this useful post
Reply all
Reply to author
Forward
0 new messages