This project has been deprecated
Due to the immenent switch from Hockey to App Center, this project has been deprecated. Minor updates may still be made, but these should not be counted on in any way. No pull requests will be accepted at this point. Any issues are unlikely to be addressed.
libhockey
libhockey is a wrapper around the Hockey App REST API. It's aim is to be a simple and easy to use as possible.
It doesn't cover every single API, but does the basics. Feel free to open an issue or a pull request for API support.
Getting started
Just add the following and you are ready to go:
import libhockey
client = libhockey.HockeyClient(access_token="...")
Examples
Listing all versions of an app
for version in client.versions.generate_all("[app id]"):
print(version.download_url)
Uploading a build
download_link = client.versions.upload("/path/to/app.ipa", "Release notes go here")
Find new crashes in a build
current_crashes = client.crashes.groups_for_version("[app id]", "[current version id]")
previous_crashes = client.crashes.groups_for_version("[app id]", "[previous version id]")
new_crashes = list(set(current_crashes) - set(previous_crashes))
for crash in new_crashes:
print(f"({crash.number_of_crashes}) {crash.crash_file} - {crash.crash_class}:{crash.crash_method}")
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Metadata
Release files for libhockey 0.23.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| libhockey-0.23.0.tar.gz | 11.2 kB | Without provenance | Details for libhockey-0.23.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| libhockey-0.23.0-py3-none-any.whl | Python 3 | none | any | Details for libhockey-0.23.0-py3-none-any.whl |
Total release size: 23.1 kB
Release files / libhockey-0.23.0.tar.gz
| Download URL | libhockey-0.23.0.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d876ee53452eafabec0d53babf0f7b394506eb0de07a6fc3440849ef54a0316b
|
|
BLAKE2b-256 checksum How to use checksums |
0950eb551ef9f461a03d3331d0d258e042c5ca1a6897546b7c1a1ca6a7796353
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.17 CPython/3.7.4 Darwin/18.7.0
|
Release files / libhockey-0.23.0-py3-none-any.whl
| Download URL | libhockey-0.23.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87bc4dd7b1318a6199a31f441ea39e798e3ca6959cc9eb259b0a173ebc560c4b
|
|
BLAKE2b-256 checksum How to use checksums |
9cc6bbd56f8e57d65d5a1b28afce92b2f3e2a458d2373553c50adbd1a29e6aac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.17 CPython/3.7.4 Darwin/18.7.0
|
Security for libhockey 0.23.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.