Skip to content

Migrating to FCM v1 API causes dependency issues with apns2 #729

Closed
@kbunarjo

Description

When I try to install the firebase-admin package in order to migrate to FCM v1 API (https://github.com/jazzband/django-push-notifications/blob/master/docs/FCM.rst), I get this error (I am using Poetry to handle dependencies)

Because no versions of pyjwt match >2.5.0,<2.6.0 || >2.6.0,<2.7.0 || >2.7.0,<2.8.0 || >2.8.0
 and pyjwt (2.5.0) depends on pyjwt (2.5.0), pyjwt (>=2.5.0,<2.6.0 || >2.6.0,<2.7.0 || >2.7.0,<2.8.0 || >2.8.0) requires pyjwt (2.5.0).
And because pyjwt (2.6.0) depends on pyjwt (2.6.0), pyjwt (>=2.5.0,<2.7.0 || >2.7.0,<2.8.0 || >2.8.0) requires pyjwt (2.5.0 || 2.6.0).
And because pyjwt (2.7.0) depends on pyjwt (2.7.0)
 and pyjwt (2.8.0) depends on pyjwt (2.8.0), pyjwt (>=2.5.0) requires pyjwt (2.5.0 || 2.6.0 || 2.7.0 || 2.8.0).
Because no versions of firebase-admin match >6.5.0,<7.0.0
 and firebase-admin (6.5.0) depends on pyjwt (>=2.5.0), firebase-admin (>=6.5.0,<7.0.0) requires pyjwt (>=2.5.0).
Thus, firebase-admin (>=6.5.0,<7.0.0) requires pyjwt (2.5.0 || 2.6.0 || 2.7.0 || 2.8.0).
So, because doter-server depends on both PyJWT (1.7.1) and firebase-admin (^6.5.0), version solving failed.

It looks like the apns2 package (which is used for APNS service in this package) requires pyjwt that's less than v2.5.0 but firebase-admin requires one that is >=2.5.0

FWIW, it looks like this is actually an issue with apns2 referencing the wrong version: Pr0Ger/PyAPNs2#133

Does anyone know how to get around this? Am I doing something wrong?

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions