no deviceToken found in ParseInstallation

[SebastienANTOINE]

Hello,

I got this issue 1 month ago, and there is no way I found to resolve it.

installation = {ParseInstallation@4486} dataAvailability = {HashMap@4490} size = 9 0 = {HashMap$HashMapEntry@4502} "localeIdentifier" -> "true" 1 = {HashMap$HashMapEntry@4503} "appVersion" -> "true" 2 = {HashMap$HashMapEntry@4504} "deviceType" -> "true" 3 = {HashMap$HashMapEntry@4505} "appIdentifier" -> "true" 4 = {HashMap$HashMapEntry@4506} "installationId" -> "true" 5 = {HashMap$HashMapEntry@4507} "parseVersion" -> "true" 6 = {HashMap$HashMapEntry@4508} "user" -> "true" 7 = {HashMap$HashMapEntry@4509} "appName" -> "true" 8 = {HashMap$HashMapEntry@4510} "timeZone" -> "true"

Parse version 1.10 and 1.11 got the problem. It used to working this summer and now nothing since I clear my _installation class table on cloud

Where is my deviceToken ? Still null and I canot get push on my device without it.

After running PushService in debug mode I found something that could gave this issue

private static boolean checkResolveInfo(Class<? extends BroadcastReceiver> clazz, List<ResolveInfo> infoList) if your app id is different than your package name this method return false and gcmSupportLevel return false and it should not;

Regards

[shtayyat]

I am having the same problem when i request the deviceToken as in this code:

ParseInstallation.getCurrentInstallation().saveInBackground(new SaveCallback() { @Override public void done(ParseException e) { System.out.println("parse parseRegId " + ParseInstallation.getCurrentInstallation().get("deviceToken")); } });

Response: "parse parseRegId null"

[teodorpenkov]

Im having the same issue. What can be done here?

[parse-github-bot]

Thank you for opening this issue. It seems your issue is related to push notifications. Please see our guide for opening a push related issue. It contains some quick debug steps and what information should be added to this issue.

[TomWFox]

Closing this as no one has reported this issue recently, and we don't have the resources to investigate these historic reports.

Please ask me to reopen if you experience this issue in the latest version of this SDK.

[SmatchyLaPaglia]

@TomWFox I am having this issue in Xamarin.Forms, should that be brought up in a different place?

[TomWFox]

No sure so I'll reopen for now :) If you have anymore details to share or would like to contribute a fix that would be very welcome.

[SmatchyLaPaglia]

@TomWFox all I can tell you is that to fix it, I had to search back through my commits for one where it didn’t happen, and then by-hand cut and paste all of the changes I made.

So basically I branched an old commit and did a sort of “manual merge” from the failing commits.

As far as I can tell the one that is working is now identical to the one that wasn’t working, except for the fact that it does actually work.