Closed nilsreichardt closed 11 months ago
Hi! Please share what does this show for you:
app-store-connect builds beta-details "57fcc640-c9ab-43dd-8b8c-874d1a34da17"
$ app-store-connect builds beta-details "57fcc640-c9ab-43dd-8b8c-874d1a34da17"
Get Build Beta Details for Build 57fcc640-c9ab-43dd-8b8c-874d1a34da17
-- Build Beta Detail --
Id: 57fcc640-c9ab-43dd-8b8c-874d1a34da17
Type: buildBetaDetails
Auto notify enabled: True
External build state: IN_BETA_TESTING
Internal build state: IN_BETA_TESTING
I presume you manually submitted this build to TestFlight later?
No, looking in App Store Connect the build (build number 515) isn't submitted yet (Ready to submit).
No idea what might have caused that. I'll add some additional logging to the step which waits until the build is processed and always output both the build and its beta details info once they are detected as processed and waiting halts. That should shed some more light on what is going on.
I'll let you know once this is ready.
@nilsreichardt, please upgrade to version 0.44.1 and let me know when this happens again.
Then we should see the exact build processing state, external build state and internal build state after processing was completed right from app-store-connect publish
logs, which hopefully reveals why the submission failed.
Thanks @priitlatt. Here are the logs:
https://github.com/SharezoneApp/sharezone-app/actions/runs/6196403244/job/16822974351
How often does this issue occur? All the statuses seem correct, which makes me think whether it is some glitch on Apple's side of things.
Workflow ID | Deployment Status | Error Message |
---|---|---|
386 | ✅ | |
385 | ✅ | |
384 | ✅ | |
383 | ✅ | |
382 | ❌ | GET https://api.appstoreconnect.apple.com/v1/builds/e7ee7e4e-3494-4757-970b-73be6a74c0a9/buildBetaDetail returned 404: The specified resource does not exist - There is no resource of type 'buildBetaDetails' with id 'e7ee7e4e-3494-4757-970b-73be6a74c0a9' |
381 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
379 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
378 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
377 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
376 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
375 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
374 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
373 | ✅ | |
372 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
371 | ✅ | |
370 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
369 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
368 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
367 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
366 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
365 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
364 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
363 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
362 | ❌ | POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions returned 422: The build is not in a valid processing state for this operation. - The build is not in a valid processing state for this operation. |
Here is the code we use to deploy the macOS app:
app-store-connect publish \
--path $PACKAGE_NAME \
--beta-group=alpha \
--testflight \
--release-type=AFTER_APPROVAL \
--whats-new "$SHORT_LAST_COMMIT_MESSAGE"
This was quite a mouthful, but I think it finally boils down to the fact that just plain wrong build is looked up after initial upload (for example here, and then consequently operations on this wrong build fail.
@nilsreichardt Fix is now available in version 0.45.1.
Awesome, thanks for the great work! I created a PR to use the new version 👍
Sometimes it works, sometimes we get the following issue:
v0.43.0