[PR #390] [MERGED] Show usesNonExemptEncryption in builds list output #492

New issue

Closed

opened 2026-02-26 22:31:12 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 22:31:12 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/rudrankriyam/App-Store-Connect-CLI/pull/390
Author: @rudrankriyam
Created: 2/1/2026
Status: ✅ Merged
Merged: 2/1/2026
Merged by: @rudrankriyam

Base: main ← Head: feature/build-encryption-status

📝 Commits (1)

398ad34 Show usesNonExemptEncryption in builds list output

📊 Changes

2 files changed (+21 additions, -6 deletions)

View changed files

📝 internal/asc/client_builds.go (+1 -1)
📝 internal/asc/output_builds.go (+20 -5)

📄 Description

Summary

Add Encryption column to builds list table and markdown output
Display encryption status as "required" (needs declaration), "exempt", or "n/a"
Change UsesNonExemptEncryption from bool to *bool to properly handle null values from API

Why this matters

The usesNonExemptEncryption field is important for App Store submissions:

If true (shown as "required"): the build uses non-exempt encryption and requires an approved encryption declaration before submission
If false (shown as "exempt"): the build is exempt from encryption requirements
If null (shown as "n/a"): no encryption information available

This helps users quickly identify which builds need encryption declarations before they can be submitted to the App Store.

Test plan

Run asc builds list --app <app-id> and verify the new Encryption column appears
Verify builds show appropriate values (required/exempt/n/a)
Test with --output markdown to confirm markdown table also shows the column

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/rudrankriyam/App-Store-Connect-CLI/pull/390 **Author:** [@rudrankriyam](https://github.com/rudrankriyam) **Created:** 2/1/2026 **Status:** ✅ Merged **Merged:** 2/1/2026 **Merged by:** [@rudrankriyam](https://github.com/rudrankriyam) **Base:** `main` ← **Head:** `feature/build-encryption-status` --- ### 📝 Commits (1) - [`398ad34`](https://github.com/rudrankriyam/App-Store-Connect-CLI/commit/398ad3414c3d658240fd097518c058b7f0fafb94) Show usesNonExemptEncryption in builds list output ### 📊 Changes **2 files changed** (+21 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `internal/asc/client_builds.go` (+1 -1) 📝 `internal/asc/output_builds.go` (+20 -5) </details> ### 📄 Description ## Summary - Add `Encryption` column to builds list table and markdown output - Display encryption status as "required" (needs declaration), "exempt", or "n/a" - Change `UsesNonExemptEncryption` from `bool` to `*bool` to properly handle null values from API ## Why this matters The `usesNonExemptEncryption` field is important for App Store submissions: - If `true` (shown as "required"): the build uses non-exempt encryption and requires an approved encryption declaration before submission - If `false` (shown as "exempt"): the build is exempt from encryption requirements - If `null` (shown as "n/a"): no encryption information available This helps users quickly identify which builds need encryption declarations before they can be submitted to the App Store. ## Test plan - [ ] Run `asc builds list --app <app-id>` and verify the new Encryption column appears - [ ] Verify builds show appropriate values (required/exempt/n/a) - [ ] Test with `--output markdown` to confirm markdown table also shows the column --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>