Skip to content

[Docs] Document how a bare kobiton-store:<APP_ID> resolves to a version #110

Description

@informramiz

Summary

app install documents the explicit pair — --app-id plus --app-version-id — and the test run example pins its runner by version, --runner kobiton-store:v762538. In the same line, that example passes the app as a bare ID:

kobiton test run --app kobiton-store:662537 --runner kobiton-store:v762538 -u 3e4e7fe7 uiautomator

The requirement line above it says only:

"each a Kobiton App Repo ID (kobiton-store:<APP_ID> or kobiton-store:v<APP_VERSION_ID>)"

The bare form is explicitly accepted, so this is not a bug report — it is a request to state what it does. Nowhere on the page does it say how the bare form resolves: newest version, first version, or the version bound at upload time.

It matters because the two identifiers are genuinely distinct: our upload returned an App ID and a separate Version ID, and app install's explicit-option form takes both (--app-id <id> --app-version-id <vid>) rather than the App ID alone. Since the two are not interchangeable there, a reader has no way to tell what a bare App ID resolves to in test run. We did not test a bare App ID against an app with several versions, so we are asking what the rule is rather than reporting a wrong outcome. Stating it on the page costs a sentence and removes the guesswork.

Asks

  1. State the bare-ID resolution rule on the page — one sentence is enough.
  2. Consider pinning both identifiers in the example, so the form most likely to be copied is the unambiguous one.

Metadata

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