This is an open discussion about the pending Unity Android Push Plugin changes.
Please list concerns, requests, and feedback here.
Update plan sounds great, really appreciated (we receive a ton of crash reports currently).
If possible please don't require a newer appcompat, appsupport or google play libraries as used with the current plugin. Many Unity projects are already on the DEX 64K limit and updating these libraries is often not possible.
We just got a second version/package uploaded. It's available in the master branch now, and will be "official" in the versioned branch in the next version of the SDK. (You can use it now, it's finished)
The new one is Google Play Services 8.4.0, appcompat-v7-24.2.0, support-v4-23.4.0, API 24.
We will review this thread Tomorrow, June 7, 2017, to determine which version combination is next highest priority.
After lots of testing, I've determined what we can do, and what we're not likely to do.
PlayServices version: First, the two supported versions of Google Play Services are 8.4.0 and 10.0.1. If you require any either of these versions specifically, then you can use the plugin provided. Any unlisted version after 8.4.0, then you're probably going to have to build the plugin yourself, using our public source.
API Version: Our plugins work with API 25 out of the box. The 10.0.1 plugin comes with appcompat-v7-25.1.1.aar. If you wish to target API 21-24, then you need to replace the appcompat file with a version matching your Android API target version. For example, if you wish to target API 21, you need to retrieve appcompat-v7-21.0.3.aar from your own AndroidSDK, remove appcompat 25, and replace it with yours. We can't get API 16-19 to work, so you have to stick with Lollipop (API 21) or higher, or not use our push plugin.
We will not be publishing any additional plugins targeting older versions of any dependencies described. According to the Google Developer Dashboard, at the time of writing this post, API 21 and higher represents 71.5% of the Android market.
You should rebuild your own plugins to define min version as 21 and higher to match, and ensure compatibility and buildability.
Please share if you have any additional questions or concerns.
Thanks for the effort you put into making the push functionality working. I'm curious about your suggestion to use the Playfab API without the plugin, because I dont need the additional functionality. The only thing I need is that a text message appears in the clients push notification area (so no icon, sound, customData parsing, no advanced things like sheduling or receiving the message in-game). I would be nice to have instructions on that (like a "minimum guide for minimum functionality").
What I learned from your existing guides is how to set up android push notifications in the playfab game manager by delivering the server key from the firebase project. And how I can register a client via ClientAPI/AndroidDevicePushNotificationRegistration. But there are two open points I didn't find information about:
7 People are following this question.