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

apns2 0.7.2 requires PyJWT<2.0.0,>=1.4.0, but you have pyjwt 2.1.0 which is incompatible. #133

Open
aabanaag opened this issue Jul 29, 2021 · 25 comments

Comments

@aabanaag
Copy link

setup.py was updated but it seems that it didn't apply properly still gets an error if PyJWT is 2.1.0

@babus
Copy link

babus commented Aug 3, 2021

@aabanaag Did you install from pypi or master branch? The changes from master branch are not yet released in pypi. I'm too waiting for the author to release the same.

@alimirjahani7
Copy link

@Pr0Ger Can you please release the master?

@aabanaag
Copy link
Author

aabanaag commented Aug 6, 2021

@aabanaag Did you install from pypi or master branch? The changes from master branch are not yet released in pypi. I'm too waiting for the author to release the same.

from pypi

@anhphamt
Copy link

anhphamt commented Sep 3, 2021

Can someone help with a work-around here? I got the same issue.

@AlexJMohr
Copy link

Hey @Pr0Ger, please release an update to PyPi

@nik13
Copy link

nik13 commented Nov 6, 2021

Same issue. Please push update to pypi!

@andrewsanchez
Copy link

You can pin your dependencies to specific commit. For example, using poetry: https://python-poetry.org/docs/dependency-specification/#git-dependencies

@levinotik
Copy link

Bump. Can you push a new release to PyPI please?

@levinotik
Copy link

@andrewsanchez do you by chance know how to specify a specific commit as a dependency when using a requirements.in file with pip-tools?

@AlexJMohr
Copy link

@levinotik

# requirements.in
apns2 @ git+https://github.com/Pr0Ger/PyAPNs2.git@5e4a938

output:

# requirements.txt
apns2 @ git+https://github.com/Pr0Ger/PyAPNs2.git@5e4a938
    # via -r requirements.in
cffi==1.15.0
    # via cryptography
cryptography==36.0.0
    # via apns2
h2==2.6.2
    # via hyper
hpack==3.0.0
    # via h2
hyper==0.7.0
    # via apns2
hyperframe==3.2.0
    # via
    #   h2
    #   hyper
pycparser==2.21
    # via cffi
pyjwt==2.3.0
    # via apns2

@madhavSoni
Copy link

Any status on this issue? We were using Django Push notifications which depends on this library but have another library that requires a PyJWT greater than 2.0. Any thoughts or suggestions on how to proceed and have everything compatible?

@johney4415
Copy link

there have some strange the latest version 0.7.2 required pyjwt = ">=2.0.0" in toml file but 0.7.2 release note and pypi required pyjwt < 2.0.0

toryth pushed a commit to toryth/django-push-notifications that referenced this issue Jul 4, 2022
apns2 https://github.com/Pr0Ger/PyAPNs2/issues has some serious issues. It looks like master is not locked into a sub 2 PyJWT versions, but, what is in pypi Pr0Ger/PyAPNs2#133 (comment)

Author seems to be unresponsive despite it being an old and easy issue to fix.

It also appears that old versions of PyJWT have security issues. This repo gives me bad vibes. But this should at least unblock us for now.
@harikvpy
Copy link

+1

@github-actions
Copy link

github-actions bot commented Jun 1, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Jun 1, 2023
@daveisfera
Copy link

This is still an issue

@DanielSchiavini
Copy link

+1

@AzikDeveloper
Copy link

Any status on this ?

@github-actions github-actions bot removed the stale label Jun 2, 2023
@biiit
Copy link

biiit commented Nov 13, 2023

In case you use pipenv I was able to install it with the specific master branch commit with the following command:

pipenv install "git+https://[email protected]/Pr0Ger/PyAPNs2.git@aac4bd3494670b8090774cb051798cfac5e0ed6a#egg=apns2"

@Cair06
Copy link

Cair06 commented Jan 12, 2024

This is still an issue

@itayAmza
Copy link

itayAmza commented Jan 25, 2024

A temporary solution
In my requirements.txt:

# django-push-notifications==3.0.2
# Point temporaraly to a forked version of django-push-notifications with support for aioapns, to avoid using unamaintained apns2
git+https://github.com/pomali/django-push-notifications.git@master#egg=django-push-notifications
aioapns==3.1

Seems to fix the issue.
Just make sure that git is installed in your environment, In my case, docker container, I had to add RUN apk add --no-cache git to my DockerFile

@ssyberg
Copy link

ssyberg commented Mar 8, 2024

still an issue!

@usgitAz
Copy link

usgitAz commented Mar 11, 2024

still an issue!!!!!!

@CoderMungan
Copy link

have any update ?

@pangyifish
Copy link

Pls 🥺🥺🥺🥺❤️❤️❤️❤️❤️

@JelleZijlstra
Copy link

I just released https://pypi.org/project/compat-fork-apns2/ based on the master branch of this repo; it works with pyjwt 2. Feel free to use it if you would like to use apns2 with pyjwt 2.

Unfortunately it still doesn't work with Python 3.10 and higher and that's harder to fix (compat-fork#3).

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

No branches or pull requests