This release is a pre-release and may not be stable for production use.
pyxpo-application
The installed app's own identity for pyxpo apps: name, id, version, build number, install time and signing details. The API follows expo-application.
pip install pyxpo-application
[tool.pyxpo]
modules = ["application"]
import pyxpo_application as Application
print(Application.application_name, Application.application_id)
print(Application.native_application_version, Application.native_build_version)
installed = await Application.get_installation_time_async() # timezone-aware datetime (UTC)
Every name also has its expo-application spelling (Application.applicationId,
Application.getInstallationTimeAsync).
Constants
Read once at app start. None on the desktop.
application_name: the name on the home screenapplication_id: bundle identifier (iOS) or package name (Android)native_application_version:CFBundleShortVersionString/versionName, for example"1.2.0"native_build_version:CFBundleVersion/versionCode, as a string
Functions
| Function | Platforms | Returns |
|---|---|---|
get_installation_time_async() |
iOS, Android | datetime (UTC). iOS: creation time of the Documents folder |
get_last_update_time_async() |
Android | datetime (UTC) of the last install or update |
get_android_id() |
Android | ANDROID_ID: unique per signing key, user and device; changes on factory reset |
get_install_referrer_async() |
Android | Google Play install referrer. Fails without the Play Store (most emulators) |
get_ios_id_for_vendor_async() |
iOS | identifierForVendor, or None before the first unlock |
get_ios_application_release_type_async() |
iOS | ApplicationReleaseType: SIMULATOR, DEVELOPMENT, AD_HOC, ENTERPRISE, APP_STORE |
get_ios_push_notification_service_environment_async() |
iOS | "development", "production" or None |
Calling a function on a platform it does not list raises NotSupportedError; so does every function on
the desktop.
On Android the module adds the com.android.installreferrer:installreferrer library.
Permissions
None.
Metadata
Release files for pyxpo-application 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyxpo_application-0.1.0a1.tar.gz | 8.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyxpo_application-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.2 kB
Release files / pyxpo_application-0.1.0a1.tar.gz
| Download URL | pyxpo_application-0.1.0a1.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86e7be0bb25d2316c2ff50b1a333046eba8fc66ba320672a239ea67f4348a607
|
|
BLAKE2b-256 checksum How to use checksums |
46e6498caa861b402a43d37550f2f8dc6e97cc9c5b45a0f2c18c46d5088d25c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / pyxpo_application-0.1.0a1-py3-none-any.whl
| Download URL | pyxpo_application-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88d6839095e2036a43ebdddb8775d27f0a5e5904d906e956ceaca017142f256e
|
|
BLAKE2b-256 checksum How to use checksums |
5ee52fa53bc0ed36f814e586b9171c1561b6fdf59c0296efdf00f37bb4e0c312
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency log