# Group ID, Artifact ID and Version of Ignition Perspective Android App - APK

**URL:** <https://forum.inductiveautomation.com/t/group-id-artifact-id-and-version-of-ignition-perspective-android-app-apk/56873>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [March 4, 2022, 11:53pm UTC](https://forum.inductiveautomation.com/t/group-id-artifact-id-and-version-of-ignition-perspective-android-app-apk/56873 "2022-03-04T23:53:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsorlie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jsorlie/32/3645_2.png) [@jsorlie](https://forum.inductiveautomation.com/u/jsorlie)\
**Post date:** [March 4, 2022, 11:53pm UTC](https://forum.inductiveautomation.com/t/group-id-artifact-id-and-version-of-ignition-perspective-android-app-apk/56873/1 "2022-03-04T23:53:06Z")

</div>

To upload the [Ignition Extras](https://inductiveautomation.com/downloads/extra-material) \> [Ignition Perspective Android App - APK](https://files.inductiveautomation.com/release/perspective/android/Ignition_Perspective_1.0.3.apk) into our enterprise workflow repository, I need to know three GAV coordinates for the APK snapshot:

- groupId
- artifactId
- version

Is there some way to inspect the APK to find the Group ID and Artifact ID that were specified when the APK snapshot was built? The current download would appear to be version 1.0.3

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 4, 2022, 11:57pm UTC](https://forum.inductiveautomation.com/t/group-id-artifact-id-and-version-of-ignition-perspective-android-app-apk/56873/2 "2022-03-04T23:57:04Z")

</div>

I’m a bit surprised at the idea you are _ **allowed** _ to rebuild these. Are you sure that’s the case?

---

<div class="post-metadata">

**Author:** ![jsorlie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jsorlie/32/3645_2.png) [@jsorlie](https://forum.inductiveautomation.com/u/jsorlie)\
**Post date:** [March 5, 2022, 12:00am UTC](https://forum.inductiveautomation.com/t/group-id-artifact-id-and-version-of-ignition-perspective-android-app-apk/56873/3 "2022-03-05T00:00:32Z")

</div>

I don’t need to rebuild it, just upload it into a repository. For this we need to know the [unique project identifiers](https://www.baeldung.com/maven#introduction-3). This would be in the pom.xml used to build the downloadable APK.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 5, 2022, 12:08am UTC](https://forum.inductiveautomation.com/t/group-id-artifact-id-and-version-of-ignition-perspective-android-app-apk/56873/4 "2022-03-05T00:08:41Z")

</div>

I think you are confused. Android apps aren’t identified by groupId, artifactId, and version coordinates like a Maven artifact.

You may be uploading the APK into a repository that expects these things, in which case you’re free to set these to whatever value you’d like.

From what I can tell the package name we use is `com.inductiveautomation.perspectiveapp`, if that helps.

---

<div class="post-metadata">

**Author:** ![jsorlie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jsorlie/32/3645_2.png) [@jsorlie](https://forum.inductiveautomation.com/u/jsorlie)\
**Post date:** [March 5, 2022, 12:37am UTC](https://forum.inductiveautomation.com/t/group-id-artifact-id-and-version-of-ignition-perspective-android-app-apk/56873/5 "2022-03-05T00:37:37Z")

</div>

Thanks both @Kevin.Herron and Phil (@pturmel)

yes dazed and confused I am... I will run with this.

> com.inductiveautomation.perspectiveapp

The learning moment here is one only needs to come up with [a unique identifier](https://www.baeldung.com/maven#introduction-3) within the context of the repository where the object will reside.