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

IOS notification return delivered true but not getting notification on mobile #548

Open
jadamdipak opened this issue Jan 15, 2020 · 5 comments
Assignees

Comments

@jadamdipak
Copy link

Ruby: 2.4
Rails 4.2
Everything working perfactly even response is also correct but didn't get the notification

#<Rpush::Client::ActiveRecord::Apns::Notification id: 13823, badge: nil, device_token: "xyz...", sound: "default", alert: "New care request has been created by dipak client.", data: "test", expiry: 86400, delivered: true, delivered_at: "2020-01-15 13:27:12", failed: false, failed_at: nil, error_code: nil, error_description: nil, deliver_after: nil, created_at: "2020-01-15 13:27:11", updated_at: "2020-01-15 13:27:11", alert_is_json: false, type: "Rpush::Client::ActiveRecord::Apns::Notification", collapse_key: nil, delay_while_idle: false, registration_ids: nil, app_id: 13, retries: 0, uri: nil, fail_after: nil, processing: false, priority: nil, url_args: nil, category: nil, content_available: false, notification: nil>

Please help me for this where I can debug

@jadamdipak
Copy link
Author

@adis-io @aried3r

@aried3r
Copy link
Member

aried3r commented Feb 21, 2020

Hey! You could begin by manually sending notifications to your test device.

There's various ways, but maybe if you're on a Mac you can use this app to debug it. If that works, we know that it's an issue with Rpush and not APNs or your app.

@Hopperman
Copy link

could this possibly relate to my issue #556 ? @jadamdipak @aried3r
My problem is similar in that the response says everything went perfectly, even though I sent it to a phone with disabled notifications / borked device token.

@stale
Copy link

stale bot commented Oct 12, 2021

This issue has been automatically marked as stale because it has not had recent activity. If this is still an issue, please leave another comment. This issue will be closed if no further activity occurs.
Thank you for all your contributions!

@stale stale bot added the stale label Oct 12, 2021
@aried3r aried3r removed the stale label Oct 18, 2021
@benlangfeld benlangfeld self-assigned this Sep 5, 2024
@benlangfeld
Copy link
Collaborator

I suspect this to be a duplicate of #556 and equally related to #604 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants