As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Dear Kinvey team,
First of all, thank you for your Android SDK update.
Previously we have this problem: https://support.kinvey.com/support/discussions/topics/12000013051
But there is the same problem.
Is it any updates in guidelines?
Thanks in advance!
I also shared this information with you in a private email.
You are currently using the Android SDK v3.0.0 BETA-02. The call to initialize for BETA-02 is as follows.
For BETA-02: myClient.push().initialize(getApplication());
However, with Android SDK v3.0.0 BETA-04, the call changed and the documentation was updated to reflect the functionality in BETA-04 as follows.
For BETA-04: myClient.push(GCMService.class).initialize(getApplication());
We strongly recommend that you upgrade to the new non-BETA version of Android v3.0.0 and use the new functionality to perform the initialization/registration of push rather than continue to use the BETA-02 version of Android.
Either way, when you rebuild after either making changes or upgrading to SDK 3.0.0, you should use the "Build-Clean project" feature of Android Studio to build everything from scratch and pick up anything new as part of the build. This is especially true if you upgrade to SDK 3.0.0 rather than remain on BETA-02.
Please let us know how you would like to proceed.
The Forum post that you reference is over two years old and though similar to your current problem, it is not likely relevant to today's Android SDK and therefore it isn't helping us much with your particular version of this problem.
I have asked the Kinvey Android team to confirm that our current push guide is up to date for the Android SDK v3.0.0 Beta-04. I will update you as soon as I hear back from them. The push guide for Android SDK v3 can be found at the following URL.
I assume that you are using this guide to configure and send your push notifications, is that correct?
Please provide us with a step by step review of the problem that you are having. Is it with the configuration of Android push itself or with sending push notifications to devices. The more details you can provide the better.
Please reproduce the problem and provide us with the timestamp, including timezone of when you reproduced the problem so that we can cross-reference our server logs for a possible root cause of your problem.
Also, please send me the text of the push message that you send that fails when you reproduce the problem.
I see in our server logs that the app is sending pushes successfully but I did not see a record of any device registering for push. When did you initially register your devices for push?
I am also going to respond to you via email and ask a couple of questions that will require you sharing information that you will not want posted on a public forum like this one.
We look forward to hearing back from you.
We believe that the documentation should be current with the latest SDK release. At your convenience, please review the updated documentation and let us know if you are satisfied with the changes ornot.