App Store code signing show "Beta Profile"

I followed this instruction to manually re-sign my ipa

To be clear, DTS doesn’t support folks re-signing iOS apps. If you need to re-sign an app, the best path forward is to distribute an Xcode archive (.xcarchive) and then re-sign that using Xcode.

However, I don’t think that’s the issue here. Rather, it sounds like you’re trying to run distribution-signed code. That won’t work. See Don’t Run App Store Distribution-Signed Code.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I discovered the error when I failed to launch the app in TestFlight. I still continue to submit for App Review and obviously, it got rejected. Attached is the crash report.

The above steps are my troubleshooting to make sure the app is signed using the Apple Distribution certificate and the correct Provisioning Profile.

This issue started after I renewed the expired Apple Distribution certificated. So, I suspect the issue is with the certificate. (I have re-generated at least two times.)

Sorry I didn’t respond sooner; I wasn’t notified of your reply )-:

Thanks for the crash report. This suggests that you don’t have a code signing problems. Rather, the presence of the Last Exception Backtrace section indicates that your app is up and running and then threw a language exception.

The backtrace on that exception is interesting:

Last Exception Backtrace:
0 CoreFoundation  … __exceptionPreprocess + 164
1 libobjc.A.dylib … objc_exception_throw + 88
2 munsblog        … 0x1029c0000 + 33407840
3 munsblog        … 0x1029c0000 + 35102404
4 UIKitCore       … -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 320

Frame 4 indicates that UIKit is calling one of your app delegate methods. Frame 3 is your app delegate method implementation. It calls some other method in your code, frame 2, which throws a language exception.

To make progress with this you’ll need to uncover the identity of your code in frames 3 and 2. For advice on how to do that, see Adding identifiable symbol names to a crash report.

Also, my experience is that many problems like this aren’t related to code signing but rather they’re caused by a difference between your Debug and Release build. I have a post, Isolating Code Signing Problems from Build Problems, that explains how you can tease these apart.

Finally, if you reply here, please tag me by adding @DTS Engineer to your reply. That should improve the chances of forums notification me of your follow-up.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi Eskimo,

Thank you for confirming it is not a Code Signing issue. I have spent the last few days to symbolicate a crash report. I found an open-source app MacSymbolicator that requires *.dSYM, which is available in .Net MAUI. Obviously, I no longer have it for the version I submitted to App Store. I must remember to keep it in future submissions.

After creating a new build and uploading it to TestFlight, the app launches successfully. I guess my efforts to debug the app for the past two months have removed the bug. Also, I realized I cannot use "xcrun" to sideload the app signed using a Distribution Provisioning Profile. I must use TestFlight even though it is slow and cumbersome.

The app has been successfully updated in both App Store and Mac App Store. Thank you very much.

@DTS Engineer