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

Feature for API keys in Ios #146

Open
knvpk opened this issue May 10, 2017 · 9 comments
Open

Feature for API keys in Ios #146

knvpk opened this issue May 10, 2017 · 9 comments

Comments

@knvpk
Copy link

knvpk commented May 10, 2017

Apple has started giving API keys instead of certificates for push notification. This makes life easy rather than working with request signing, changing them from cer to p12 etc etc.

Also refer this davibennun/laravel-push-notification#173

@knvpk
Copy link
Author

knvpk commented May 22, 2017

Is anybody there?

@seyfer
Copy link
Collaborator

seyfer commented Jul 30, 2017

@pavankumarkatakam, I need to have a look at it.
If any participants would like to add their contributions - you are welcome.

@seyfer
Copy link
Collaborator

seyfer commented Aug 4, 2017

@Ph3nol, I would try to implement new API way to work with APNS with help of this library - edamov/pushok

Seems like Zend library not actively supported zendframework/ZendService_Apple_Apns#45 (comment)
So, when edamov/pushok will implement a functionality to work with certificates - I think it's a good idea to replace Zend with edamov/pushok completely in future.

@seyfer
Copy link
Collaborator

seyfer commented Aug 9, 2017

@Ph3nol, since edamov/pushok supports only php 7.0+ I will mark our v2.3 to support only 7.0+ also.

@seyfer
Copy link
Collaborator

seyfer commented Aug 9, 2017

@Ph3nol, or it's better to mark it as v3.0, because, for example, this popular laravel module https://github.com/davibennun/laravel-push-notification depends on our 2.* version.

And if we will release v2.3 with php 7.0 minimum - it will break laravel-push-notification.

I think there is a lot more packages which depend on Ph3nol/NotificationPusher v2..
And they are for php 5.
.
That's why v3.0 will be better.

@seyfer seyfer added the 3.x label Nov 1, 2017
@seyfer seyfer added this to the 3.0 milestone Nov 1, 2017
@Jacse
Copy link

Jacse commented Jan 30, 2018

Any update on this, @seyfer ?

@seyfer
Copy link
Collaborator

seyfer commented Jan 30, 2018

Well, it needs to be done, definitely.
But I need to have resources for that. What I need: time, android and ios devices(don't have it) and simple ionic app to just accept notifications (do not have experience with it at the moment, but will).

The plan is:

  • to buy some old iPhone first because it needs to be connected to PC for development.
  • then have a look at ionic and craft simple app for testing (which is simple)
    Only after that, I would dive into development, when I will be able to test what I'm developing.
    At the moment when I have written messages above I had an ios device, now I haven't it, and also have less time.

What I could do is to add TODO section in the readme and hopefully, somebody would like to participate.

@eerison
Copy link

eerison commented Feb 1, 2019

@seyfer Thanks for your comment about edamov/pushok I was problem with another lib that was using old apple api and my application stop send notification :(

So I change to this lib (edamov/pushok) and to be working perfectly :)

But I can help you implement this lib here and make new release 3.x

@seyfer
Copy link
Collaborator

seyfer commented Feb 3, 2019

@eerison you can, if you have time.
It is about replacing ApnsAdapter implementation here to use edamov/pushok instead of Zend_Apns, with the same interface.

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