Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when registering device for push notifications from channels. #10

Closed
vikram25897 opened this issue Jul 27, 2020 · 2 comments
Closed
Assignees
Labels
status: done This issue is considered resolved. type: bug This issue reports a bug.

Comments

@vikram25897
Copy link

I have added FCM server key on the dashboard, and I am trying to register my device for push notifications from channels like this:
await client.addPushChannels(fcmToken, PushGateway.fcm, channelSet);

However I am receiving this error:

E/flutter (13240): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PubNubException: null error: Invalid type argument
E/flutter (13240): #0 new PubNubException (package:pubnub/src/core/exceptions.dart:6:29)
E/flutter (13240): #1 getExceptionFromDefaultResult (package:pubnub/src/dx/_utils/exceptions.dart:31:10)
E/flutter (13240): #2 getExceptionFromAny (package:pubnub/src/dx/_utils/exceptions.dart:6:12)
E/flutter (13240): #3 defaultFlow (package:pubnub/src/dx/_utils/default_flow.dart:34:11)
E/flutter (13240):
E/flutter (13240): #4 PushNotificationDx.addPushChannels (package:pubnub/src/dx/push/push.dart:74:12)

I also tried calling it other way like:

await client.device(fcmToken).registerToChannels(channelSet, PushGateway.fcm);

But the error stays the same. Any ideas about what could it be?

@are are self-assigned this Jul 27, 2020
@are are added status: in progress This issue is being worked on. type: bug This issue reports a bug. labels Jul 27, 2020
@are
Copy link
Contributor

are commented Jul 27, 2020

Hi @vikram25897! I have started looking into your issue. Thanks for reporting it!

@client-engineering-bot
Copy link
Contributor

@vikram25897 this issue is addressed in v1.4.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: done This issue is considered resolved. type: bug This issue reports a bug.
Projects
None yet
Development

No branches or pull requests

3 participants