Skip to content

[feat] macOS managed version code instead of relying on version string #14631

@setoelkahfi

Description

@setoelkahfi

Describe the problem

Let me know if this duplicate or not possible.

I observed that on AppStore release for iOS, I could reuse the same version string release lane with automated version code bumped by Tauri. But it's not the case with macOS. This is my iOS Tauri conf file:

{
  "productName": "TutorialGitar 88",
  "identifier": "xyz.smbcloud.TG88",
  "version": "1.0.0",
  "bundle": {
    "iOS": {
      "developmentTeam": "team id",
      "minimumSystemVersion": "14.0"
    }
  }
}

This is my macOS:

{
  "productName": "TutorialGitar 88",
  "identifier": "xyz.smbcloud.TG88",
  "version": "1.0.0",
  "app": {
    "windows": [
      {
        "title": "TutorialGitar 88"
      }
    ]
  },
  "bundle": {
    "icon": ["icons/icon.icns"],
    "macOS": {
      "entitlements": "./Entitlements-appstore.plist",
      "signingIdentity": "signing id",
      "files": {
        "embedded.provisionprofile": "/Users/setoelkahfi/Repositories/apple-certificates/gt8/Gt8_Mac_AppStore_Provisioning_Profile.provisionprofile"
      }
    }
  }
}

.

Describe the solution you'd like

I would like to let Tauri build manage my version code for macOS so I can reuse the same version string with and upload different build with bumped version code.

Alternatives considered

What I've been using to to always bump the minor version of my macOS version string whenever I need to upload new build.

Additional context

Image Image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions