User Profile

I work in an office where there are multiple devices used to access the developer account.We constantly have the problem that when asked to enter the verification code we have no idea which device to look for it on. If you are luck it will appear on a device near by but we have people working from remote locations that also access the developer account so the verification code could be sent literally anywhere in the world.There must be some way we can limit the devices the code can be sent to so we know where to look for it. It would also be helpful if it would also tell you the name of the device it was sent to.Can somebody point me in the correct direction?

The documentation for setBadgeIdentifier:forURL: says:"Avoid adding badges to items that have not been displayed in the Finder."Does it cause any problems if it is called for items that have not been displayed in the Finder?It required a fair bit of work for the finder extension to keep track of all items seen by the finder and then only update the badge identifiers for those items. It is far simpler to notify the finder of change to a any badge identifier and have the finder ignore the call if it has not been seen.I am not planning on calling setBadgeIdentifier for all items in the monitored folder on startup but to just call it when something happens such that the badge identifier would change.Barry

I have a finder extension and have noticed that when I switched the finder display mode to 'cover flow' that a second instance of the FIFinderSync is allocated and then after that calling:[[FIFinderSyncController defaultController] setBadgeIdentifier:overlayID forURL:url];fails to set the badges anymore. I noticed that Dropbox has the same problem.Should I be using something other than [FIFinderSyncController defaultController] or is this a bug in the finder?I am running 10.13.5.

I am building apps using xcodebuild running in a Jenkins build system. The build system generates archives which are then sent to the customer.Up until I switched from xcode 7 to xcode 9 I could do this by just passing in an entitlements file to xcodebuild and use a generic developer provisioning file.This had the huge advantage that I did not need the customer to provide me with their actual provisioning files or use project specific signing certificates.But this doesn't work with xcode 9, it will not include the entitlements I pass in on the command line if I try this now.It looks like I will need to provide the actual app specific provisioning files and separate signing certificate for each app. I would really like to avoid having to do this.Is there a better way to do this?Does apple provide any documentation on best practices for developing third party apps?