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

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. crashlog-8B515F2C-530E-4779-8C09-2EB4845511E5 1.ips 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.)