Can't solve Push Commander: Register Device for Push Notifications, Is it M1 issue?

Console Missions
1

Mission: PUSH COMMANDER
Task: Register device for push notifications

Please, describe your problem here.

I followed the video and the documentation, and double-checked values. When launching my app, I expect the device to register. Far as I can tell, the async call is being issued to do the Device Registration but something is failing in the communication and I get no callback. I have debug Toast calls before and after the non-blocking Device Registration call so I think that it is getting through the Device Registration at least.

I’m on an M1 Mac and I had to use an M1 Preview Emulator GitHub - google/android-emulator-m1-preview. I wonder if this has anything to do with this failing.

2

The non-blocking call would return the result or error to the AsyncCallback object. Did you add any logging there?

3

Here are the errors I’m getting in the log:

2021-03-14 10:34:10.147 3146-3146/? E/libc: SetHeapTaggingLevel: re-enabling tagging after it was disabled is not supported
2021-03-14 10:34:10.268 3146-3171/com.example.push E/ActivityThread: Failed to find provider info for com.google.android.gms.chimera
2021-03-14 10:34:10.291 3146-3176/com.example.push E/FirebaseInstanceId: Google Play services missing or without correct permission.
2021-03-14 10:34:10.295 3146-3182/com.example.push E/FirebaseInstanceId: Google Play services missing or without correct permission.
2021-03-14 10:34:10.345 3146-3146/com.example.push E/My Debug: Before non-blocking.
2021-03-14 10:34:10.347 3146-3146/com.example.push E/My Debug: After non-blocking.
2021-03-14 10:34:10.378 3146-3176/com.example.push E/FirebaseInstanceId: Google Play services missing or without correct permission.

My Debug are my custom log messages. I also put one in each of the handlers in the registerDevice block which don’t show, so am I failing because one of the earlier error messages?

4

Looks like the Google play services is not properly configured. The last error in the log you shared provides a clue. Have you checked for errors in logcat?

Here’s a relevant discussion:

Regards,
Mark