The code was not previously signed....and the approvals were not being remembered.We are in the process of getting setup with a dev account so that we can sign and recompile all of these.Is there no way to disable this entirely? Even if the approvals were remembered, it still poses a HUGE set back to our workflow.
KramerGraphics
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
We are now able to sign using the DEV account....and that just broke everything.Previously it was asking, over and over and over, for permission to interact with other software. Now it simply will not run, instead returning an error "________ is not authorized to send apple events to ________" or similar.Now nothing works.
Appreciate all the feedback on here. Unfortunately deploying from within an app isn't a real option. The largest point of these apps is drag/drop functionality. We pull a lot of data from the files paths and names and save a lot of time.It would be a massive step backwards to require browsing to files.