You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Incompatible with urllib3 2.x - AttributeError: 'HTTPResponse' object has no attribute 'getheader' #58
The latest version of the API library (2.2.1) throws an exception when creating a notification with urllib3 2.x installed.
Error:
AttributeError: 'HTTPResponse' object has no attribute 'getheader'
The issue is in onesignal/rest.py line 43, where RESTResponse.getheader() calls self.urllib3_response.getheader(). This method was removed in urllib3 2.0 (April 2023).
The package declares urllib3>=1.25.3 with no upper bound, but the code is not compatible with urllib3 2.x.
Steps to reproduce?
1. Install onesignal-python-api==2.2.1 with urllib3>=2.0 (e.g., urllib3==2.5.0)
2. Create and send a notification using the API
3. Observe AttributeError: 'HTTPResponse' object has no attribute 'getheader'
What did you expect to happen?
The notification should be sent successfully. Either:
The SDK should be updated to use the urllib3 2.x API (.headers.get() instead of .getheader())
Or the package should pin urllib3>=1.25.3,<2 until fixed
+1 to this issue. Caused an unexpected outage recently in a project I'm working on.
Also, want to express a strong preference between the two remediation options that the SDK is updated to use urllib3 2.6.0 or higher given recent CVEs CVE-2025-66471 and CVE-2025-66418.
Reacted by Luqman, Eleazar Bernal and Trevor Hunter
Hey everyone, thanks for your patience on this as we work on a fix.
We currently have an update staged here #110. I'll follow up once a new version has been published.
Activity
plisker commentedon Dec 16, 2025
+1 to this issue. Caused an unexpected outage recently in a project I'm working on.
Also, want to express a strong preference between the two remediation options that the SDK is updated to use
urllib32.6.0 or higher given recent CVEsCVE-2025-66471andCVE-2025-66418.kolbydanner95 commentedon Jan 8, 2026
+1 any update on this?
sherwinski commentedon Jul 28, 2026
Hey everyone, thanks for your patience on this as we work on a fix.
We currently have an update staged here #110. I'll follow up once a new version has been published.
fix: add v5.11.1 package updates (#111)
github-actions commentedon Jul 29, 2026
🎉 This issue has been resolved in version 5.11.1 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀