question

Hi Zac!

I got Device Token received by other plugin. I registered with PlayFabAPI that Token, and sent via postman a push notification. I successful received that notification and app displayed it. 

I manually merged AndroidManifest. In Your default AndroidManifest You have some acitivity like this:

<service android:name=".GCM.PlayFabGcmListenerService" android:exported="false">
<intent-filter>
<action android:name="com.google.android.c2dm.intent.RECEIVE" />
<action android:name="com.google.android.c2dm.intent.REGISTRATION" />
</intent-filter>
</service>

I had a cash. Class PlayFabInstanceIDListenerService didn't found. 
When i change it to

<service android:name="com.playfab.unityplugin.GCM.PlayFabGcmListenerService" android:exported="false">
<intent-filter>
<action android:name="com.google.android.c2dm.intent.RECEIVE" />
<action android:name="com.google.android.c2dm.intent.REGISTRATION" />
</intent-filter>
</service>

Everything start working. 


Ps. Still can't received DeviceToken by Your API but solved this with another plugin. 

Hey Lukasz,

I am glad that you were able to get unblocked and sorry that you were never able to get the device token from our plugin. We will be looking into the information you provided to improve our plugin.

Thanks,

Zac

Even using your examples posted, it also fails. This is found in adb.exe logcat logs, right after the call to Init:

 (built using https://github.com/PlayFab/UnitySDK/blob/master/ClientExamples/PushNotificationExample.unitypackage . Note, I had to remove some code because there are unresolved issues to Linq in the on message received handler, but the rest was left intact). 

W/ActivityManager(  509): Unable to start service Intent { cmp=com.********/com.playfab.unityplugin.PlayFabUnityAndroidPlugin } U=0: not found
I/PlayFabUAP(19603): PlayFabUnityAndroidPlugin Service, Binding to Unity Activity
W/ActivityManager(  509): Unable to start service Intent { cmp=com.*********/com.playfab.unityplugin.PlayFabUnityAndroidPlugin } U=0: not found
D/Raydium_ts_main(  180): Report rate in 10 seconds =501

Lukasz, casticonstantinescu,

After much digging, it turns out Google changed they way push plugins need to be built. We have completed the rebuild and will be uploading the asset package after we complete testing & documenting.

Thanks for being patient, Google really caught us by surprise on this one.  

You will be able to find the plugin in our UnitySDK gitHub repo; also, I will post back here after our plugin goes live.

-Zac

Hi Zac any idea when I can pull an update or clone one of your repos that has the changes applied

We do not have a fixed release date; however, this should be available next week. 

-Zac

Hi,

I have the exact similar problem described in the main subject. However since the post date back some months ago I guess the plugin is now functionnal. I'm using the last version of playfab and the last version of the android plugin. I did not try yet to get the token from another plugin, I would like to get it works entirely with playfab's plugins.

Thanks

@maximelaffaire please review the video here: https://www.youtube.com/watch?v=f6RFXrlSlmw&t=350s it shows how to setup push notifications end to end with our plugin.

If you are getting the token through the firebase API (on your own) then most likely you have disabled our plugin in your manifest ( total guess here ) and / or something else is wrong. Without seeing your project or your manifest I have no way to tell. If you post your manifest and or code then we can take a look at it. But really you should just follow the video tutorial and it should work out of the box for you.

We had the same issue because we installed Play Game Plugin for Unity

Using Playfab notification plugins and Google play service causes version incompatibilities in .jar and .aar files (which is quite problematic), we uninstalled Google Play Game Service in order to have notification, but we still working on the issue to identify what really cause this.

Because of that our homemade Social, Achievement and Quest systems aren't working at 100%, we will post again when we have more details.