-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Push to Android won't works #3385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What version of parse-server are you running? Also, can you try with VERBOSE_PARSE_SERVER_PUSH_ADAPTER=1 before running your startup command? |
@flovilmart I'm using the version 2.3.2. Now I've got this message, and I'm trying with many Keys and SenderIds. Do I need any allowance in the GCM panel?
|
I'm not sure what the issue is, what's clear is that the SenderId don't match what the GCM is allowed to send to |
Hey, thanks for reporting this issue. Can you please add all the info specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported. |
I can tell you that everything works if I use version 2.3.2. |
Do anyone have a working structure for FCM based notification. I have configured my android client side acc. to parse docs but unable to get the notification on my device. and on IOs the error is like: ERR! parse-server-push-adapter APNS no qualified connections for com.domain.App 9adac41872d31928743e464f54116bd69579275e7f01481e6e8b2d32df31b7d8 |
I'm configure my own parse-server and everything works fine, but the push to android won't works.
Vebose log:
[13278] parse-server running on http://177.67.112.173:1337/parse verbose: REQUEST for [POST] /parse/push: { "data": { "alert": "test" }, "where": { "deviceToken": "APA91bH-BeIb8LN-ry2P7wLGpCwJUPKSV8r1nNDqwK_mlf-peMDdIUIQpoYwvgCi3x6fX0KZstKrN3goHggCx8QzgbY9Dpnl9SEMZzK6mS-qTYKQOKGtaV1ZRKt64CbRrkH0KeJDZYAQ", "deviceType": { "$in": [ "android" ] } } } method=POST, url=/parse/push, host=177.67.112.173:1337, connection=close, content-length=433, origin=http://parse.tray.com.br, user-agent=Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36, content-type=text/plain, accept=*/*, referer=http://parse.tray.com.br/apps/TrayCommerce/push/new, accept-encoding=gzip, deflate, br, accept-language=en-US,en;q=0.8,pt;q=0.6, alert=test, deviceToken=APA91bH-BeIb8LN-ry2P7wLGpCwJUPKSV8r1nNDqwK_mlf-peMDdIUIQpoYwvgCi3x6fX0KZstKrN3goHggCx8QzgbY9Dpnl9SEMZzK6mS-qTYKQOKGtaV1ZRKt64CbRrkH0KeJDZYAQ, $in=[android] verbose: RESPONSE from [POST] /parse/push: { "headers": { "X-Parse-Push-Status-Id": "zmDjajdFxQ" }, "response": { "result": true } } X-Parse-Push-Status-Id=zmDjajdFxQ, result=true verbose: sending push to 1 installations verbose: sent push! 0 success, 1 failures
Start Server:
/bin/parse-server --appId APPID --masterKey MASTERKEY --databaseURI mongodb://IP/parse --serverURL http://IP:1337/parse --cloud ./cloud/main.js --appName Commerce --push '{"android": { "senderId": "SENDERID","apiKey": "APIKEY"},"ios": {"pfx": "/etc/parse/ios.p12","passphrase": "","bundleId": "br.com.tray","production": true}}' --verbose 1
I get the SENDERID and APIKEY from Google Firebase. If I put the same data into parse.com, this feature works fine.
PS: IOs push is working
The text was updated successfully, but these errors were encountered: