Skip to content

Rewrite export compliance to use correct ASC API flow#12

Merged
trmquang93 merged 1 commit intomainfrom
feature/export-compliance-ui
Apr 8, 2026
Merged

Rewrite export compliance to use correct ASC API flow#12
trmquang93 merged 1 commit intomainfrom
feature/export-compliance-ui

Conversation

@trmquang93
Copy link
Copy Markdown
Contributor

  • Surface compliance status in BuildSelector for all builds, not just when compliance is missing (always show Edit/Manage button)
  • Enrich attached build with complianceState from builds list
  • Remove deprecated usesNonExemptEncryption from declaration API calls
  • Rewrite PATCH handler to use correct ASC API approach:
    • "No encryption": PATCH build with usesNonExemptEncryption=false
    • "Yes + algorithm": POST new declaration, then PATCH build to link it
  • Include usesNonExemptEncryption in build fields and derive compliance state as VALID when explicitly set to false

What

Brief description of the change.

Why

Why is this change needed? Link any related issues.

Closes #

How

How was this implemented? Any design decisions worth noting?

Testing

How did you test this change?

  • Tested manually against a real App Store Connect account
  • Verified no console errors in browser
  • Checked responsive layout (if UI change)

- Surface compliance status in BuildSelector for all builds, not just
  when compliance is missing (always show Edit/Manage button)
- Enrich attached build with complianceState from builds list
- Remove deprecated usesNonExemptEncryption from declaration API calls
- Rewrite PATCH handler to use correct ASC API approach:
  - "No encryption": PATCH build with usesNonExemptEncryption=false
  - "Yes + algorithm": POST new declaration, then PATCH build to link it
- Include usesNonExemptEncryption in build fields and derive compliance
  state as VALID when explicitly set to false
@trmquang93 trmquang93 merged commit 7c084e8 into main Apr 8, 2026
@trmquang93 trmquang93 deleted the feature/export-compliance-ui branch April 8, 2026 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant