GitHub user RobertWalsh opened a pull request:
https://github.com/apache/usergrid-android/pull/1
Updates. See commit details.
The UsergridAndroidSDK now uses the new Usergrid Java Client SDK jar that
updates for the new BaaS endpoint.
The Push and ActivityFeed sample apps now use Firebase Cloud Messaging in
favor of the deprecated GCM. They are also both updated to use the new BaaS
endpoint.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RobertWalsh/usergrid-android master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/usergrid-android/pull/1.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1
----
commit f168486b3631adf3910f4532260b03c9e077aa3d
Author: Robert Walsh <rjwalsh1...@gmail.com>
Date: 2016-10-05T23:33:49Z
Updated Push Sample application to use FCM instead of GCM.
Google is directing developers to now use FCM.
commit 968e2fb1b739fb92d5a1cfb755cf7c5ac951065c
Author: Robert Walsh <rjwalsh1...@gmail.com>
Date: 2017-01-05T01:10:03Z
Updates. See commit details.
The Android SDK now uses the new Java client jar that points to the new
BaaS endpoint.
Due to changes due to the new BaaS endpoint the Sample applications needed
changes as well to point to valid endpoints and BaaS orgs/apps.
The ActivityFeed sample application was modified to use Firebase Cloud
Messaging instead of the deprecated GCM. The Push sample app was modified
already to do so.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
