-
-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
No notifications are shown on Android 8 devices #334
Comments
I did some further digging. FCM should be supported, since this package depends on The problem is not server-side, but on the client. No GCM tokens are being registered for android devices (in the When using
Also, I tried the FCM format of the SenderID in config.xml, like described here (https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/INSTALLATION.md#co-existing-with-plugins-that-use-firebase), but no result. When I revert everything back to
This issue is documented here: phonegap/phonegap-plugin-push#1949 |
@raix sorry to draw this ticket to your attention, but I feel it's rather urgent. Currently no Android 8 device (rapidly growing user group) is showing notifications for every meteor cordova app using this package. Could you please confirm there is indeed a problem using this package in combination with I'm willing to contribute if you don't have the time to, If you point me in the right direction. |
@Sewdn We might need to upgrade the phonegap-plugin-push to v1.11.0 - we could also investigate upgrading to 2.x - it's a major version bump so I'd expect some api changes - but it might not be that bad I would take a pr and assist if needed, the main code to look at would be ref: https://github.com/phonegap/phonegap-plugin-push/blob/master/CHANGELOG.md |
Ok, starting on it today. I will pin the phonegap-plugin-push at 2.1.3 (and will test and develop against this version), since 2.2.x needs cordova-android 7.1.0 and Meteor 1.6.1.1 has support for cordova-android 6.4.0
|
There is not much to be changed in the Support in Android 8 for Channel Groups (https://developer.android.com/guide/topics/ui/notifiers/notifications.html#ManageChannels) and Channel Badges is supported out-of-the box in phonegap-plugin-push and needs no change on the However, there are some other breaking issues before being able to bump to No support in Meteor 1.6.1.1 for android-cordova 7.1.0Meteor 1.6.1.1 has pinned cordova-android on 6.3.0. As long as MDG doesnt upgrade to android-cordova 7.1.0 android-cordova@7.1.0 is a release of Feb 21, 2018: Previous android-cordova upgrade was done in Meteor 1.6.1: Google Services dependency, adding google-services.json configWhen using It is currently not possible adding this resource using If you dont want to change There is no other way adding this configuration file. Trying to add the resource to the
There is however a pull request being merged in Meteor@1.7 release, allowing for additional resources to be declared in The Meteor Cordova plugin breaks how 3rd party cordova plugins add extra gradle fileWhen a Cordova plugin declares post build configuration for gradle, using This issue is described here: meteor/meteor#7600 This seems strange to me, since the meteor plugin declares this extra gradle reference the way Cordova describes it (https://cordova.apache.org/docs/en/latest/guide/platforms/android/index.html#extending-buildgradle):
Adding both |
Nice investigation @Sewdn - thank you for looking into upgrading |
@Sewdn sorry for the lack of context but I'm on mobile, my phone is dying and I don't want to forget to respond to you. Below is the markdown for the (sloppy) way we got around this and got Android push working again. Building Android (post Meteor 1.6.1)Building for Android has become crazy complex due to Cordova plugin conflicts between the Google+ Cordova plugin included from Meteor Google Accounts and phonegap-plugin-push used by raix:push. See my issue on the phonegap-plugin-push repo. Pre-requisites (already committed to git):
Build steps
Once confirmed to be working, follow standard steps to sign the Building for production release
Building iOS for production releaseBefore starting, remove the Android platform to avoid build errors
Note: If builds still fail after adding the header search paths, go to |
@etyp thanks for your elaborate response and documentation about your build process for Android! I'll look into it shortly. |
Hey, I have a problem in receiving android messages with android 8.1, no error messages or anything. Notifications just don't come through even when the server says that the message was sent successfully. I tried and failed to do the long alternative method with no outcome. |
I have the same issue as @FelixOBrien. Push on debug mode is saying messages were a success. I've noticed that even sending directly from the Firebase console does not work. |
@FelixOBrien @TheRealNate Any updates? Have you guys solved the issue? |
I found a possible cause. On 8.0 apps are required to register notification
categories. Does anybody know how to do this?
…On Fri, Jul 13, 2018, 3:18 AM Naman Gupta ***@***.***> wrote:
@FelixOBrien <https://github.com/FelixOBrien> @TheRealNate
<https://github.com/TheRealNate> Any updates? Have you guys solved the
issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#334 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APg4Q21nPqYx_SJ6Bwm2Ws2rc3dj5fO-ks5uGEmwgaJpZM4TSDcH>
.
|
Yes, we need to create a channel and then assign a channel id to each type of notification for android 8 and above. But I am not sure how to do it. |
I also think this needs to be made into a separate issue because OP is not getting a server log confirming notification being sent while I am. #341 |
This fixes the problem where multiple cordova plugins attempting to use the postBuildExtras in the gradle script will simply clobber each other. The cordova provided gradle template provides a defined list for plugins to add their post build extras to so they can all play nicely together. https://github.com/apache/cordova-android/blob/73edf4de7b751ecc103e9fad3c6d71c149c9118e/bin/templates/project/app/build.gradle#L90 This fixes the problems outlined in: meteor/meteor#7600 Meteor-Community-Packages/raix-push#334
@etyp Are these steps you mentioned above still required for Meteor 1.7+ & 1.8? I am running on Meteor 1.8 and phonegap-plugin-push@2.1.3 The iOS works fine without any problem and without any modifications in the cordova/plugins/builds and I get notifications. Appreciate any pointers/help. Thanks. |
@honwlt yeah we recently did a release on Meteor 1.7 and I had to follow the same steps as I posted above. I haven't tried with 1.8 yet since we just updated, but confirmed to have the same issue while on 1.7. The items released in 1.8 don't seem to address anything related so I'd imagine this won't change until a future release. Let me know if you get stuck trying to follow those steps - I'll see if/where I can help. |
Hello. When I update phonegap-plugin-push to v2.1.3 with latest raix:push (3.4.1) the mobile app (Android) will crash with Using phonegap-plugin-push v1.11.1 works fine but I'm not sure if it supports FCM. I'm using the Thank you |
I am seeing the same issue as @killerchip |
I'm trying to update my app to using I'm using The
Anyone else having the same issue?
I'm under the impression that the app does not build correctly. |
@tparkin I solved my issue by adding the extras file that is mentioned in this post: But I'm still dealing with the error "Error: String resource ID #0x0", but that's the story of this post here :-) |
Hi!
I have been able to send notifications to android users in the past, using an older version of this package and
cordova:phonegap-plugin-push
. However, I wasn't able to send to Android 8 devices. I was using GCM, and decided to switch to FCM.I therefor updated to the newest version of plugin-push (allowed by the cordova-android version in meteor):
phonegap-plugin-push@2.1.3
raix:push@3.3.0
When I now send notifications, all iOS devices receive their messages correctly, but none are sent to android devices:
Push: Sent message "hello" to 1 ios apps 0 android apps
I didn't change my configuration files, but I added
google-services.json
incordova-build-override/platforms/android
in order to configure FCM.I also added
build-extra.gradle
following the suggestion of this comment: meteor/meteor#7600 (comment)I'm using the new Cloud Messaging API keys from
https://console.firebase.google.com/u/0/project/pentu-ad4be/settings/cloudmessaging
.In google-services.json a different API key is used then what is added to settings (I suppose this being a generic API key voor Firebase services). (I tried changing configuration to use the same Key as well).
Even for different combinations of the same user having multiple registered devices (both iOS and Android, only Android 7, only Android 8, both android 7 and 8, ...), none of the android devices are receiving messages. Users that were receiving messages with the older versions and GCM, no longer receive messages (with the same device registration data in their user profile).
I suppose something is going wrong server-side, when sending requests to firebase services, (because the app keeps logging
0 android apps
). I dont see any other logs, so I don't know if the server side code is not sending requests at all, or no valid request is being sent.Feels like I have tried everything.
What do you suggest to further debug the issue? :/
Thanks!
The text was updated successfully, but these errors were encountered: