I new to the distribution process so I appreciate any help I may get here. I wish to produce an approved app for private distribution; however, when I submit the app for authorization with the App store connect--as now required for all apps--it always gets rejected with the terse log: "asset validation failed". I note that my app also shows the warning: "SpellAnalysis isn't code signed but requires entitlements. It is not possible to add entitlements to a binary without signing it." --My app is free of all bugs screened by the compiler. --I have checked the "Automatically manage signing" option with the build panel and, although I am inclined to also select a valid signing certificate in the same panel, this option persists with the value "none" when I look for a certificate listing. Also, it looks like I am not even listed as a team member for the app. --I have checked to see that I have a valid Developer ID Application certificate in my online Account. --I have confirmed that my app bundle identifier matches my online app id listing. What could I be doing wrong? Thanks for life-line you may toss me.

I keep getting one last warning when I build my app to run: " SpellSentry isn't code signed but requires entitlements," despite having a valid developers certificate and provided an entitlements file with selected provisions. What else should I be checking for?

After replacing Big Sur OSX 11.0 with the latest 11.5, my app's AXObserverAddNotification methods fails. Here is sample code I tested from StackOverflow: https://stackoverflow.com/questions/853833/how-can-my-app-detect-a-change-to-another-apps-window AXUIElementRef app = AXUIElementCreateApplication(82695); // the pid for front-running Xcode 12.5.1 CFTypeRef frontWindow = NULL; AXError err = AXUIElementCopyAttributeValue( app, kAXFocusedWindowAttribute, &frontWindow );     if ( err != kAXErrorSuccess ){         NSLog(@"failed with error: %i",err);     } NSLog(@"app: %@  frontWindow: %@",app,frontWindow); 'frontWindow' reference is never created and I get the error number -25204. It seems like the latest Big Sur 11.5 has revised the Accessibility API or perhaps there is some permission switch I am unaware of that would make things work. What am I doing wrong?