Been working for me fine and I did one just this week. One thing you can try - go grab something called ‘RB Checker Lite’. Drag and drop the app on that and see what it tells you - that’s quite good at finding signing errors and if there is one, it may give you a hint what’s going wrong.
and it’s not Apple that’s blocking it by the way - it’s just Gatekeeper warning your users who are, fortunately, smart enough to have Gatekeeper turned on. > On 19 Jun 2015, at 16:35, John Nairn <[email protected]> wrote: > > I just posted a signed version of my app as an update and numerous users > report Apple wants to block it because I am not an identified developer. But > I signed it as directed by Apple and all within XCode. I found the details at > > https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/DistributingApplicationsOutside/DistributingApplicationsOutside.html > > <https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/DistributingApplicationsOutside/DistributingApplicationsOutside.html> > > with steps: > > 1. In project settings, sign with Developer ID identity (verifyed as valid > and current in keychain and in XCode) and insure unique bundle ID > 2. Create an Archive of the application > 3. In organizer validate the signing for distribution outside the app store - > reponse is valid > 4. In organized export as application to be distributed outside the app > store. I select team and the processes and it exports > 5. Post that version, but whenmpeople download it reports the developer > cannot be identified > > Is there any hope to distribute outside the app store? > > ------------ > John Nairn
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
