mac-app-store | 易学教程

Mac App Store: Giving up 32 bit support in favor for ARC, will existing users of 32 bit version see an update message?

阅读更多关于 Mac App Store: Giving up 32 bit support in favor for ARC, will existing users of 32 bit version see an update message?

问题 I'm considering dropping 32-bit support for in favor for Automatic Reference Counting (which is only supported for 64 bit binaries). I'd like to avoid these two scenarios with the Mac App Store: For a user of an old 32-bit Mac : who did purchase the previous version with 32-bit support: Will they see an update message for the app in the Mac App Store? If so, the (now 64 bit only) update would not work for him/her. who has not purchased the app before: will they be able to purchase the app

Turning Entitlements on in Xcode Prevents Bare Bones App From Launching

阅读更多关于 Turning Entitlements on in Xcode Prevents Bare Bones App From Launching

问题 I created a basic application in Xcode 4.2. Very simple application, I have not changed a single thing. Push run, and you get the standard base application window. If I turn entitlements on for my target and hit run, I don't get any debugger errors, but the window never comes up. I checked the logs with Console.app and got the following: First error I get: taskgated: killed com.alsbury.EntitlementsTest[pid 15903] because its use of the com.apple.developer.ubiquity-container-identifiers

Sandbox - killall Operation not permitted

阅读更多关于 Sandbox - killall Operation not permitted

I'm writing a small Mac application (in Obj-C) which runs the following command: system("killall Finder"); I wanted to see what would happen if I sandbox the app (as sandboxing will be required on June 01), and the app wouldn't work. I got the following response: killall: warning: kill -TERM 6524: Operation not permitted Is there any way to get around that? As in a specific entitlement to add or another way to run the command? Thanks in advance. Your app completely goes against the spirit of the sandbox, so there's almost no chance that the MAS reviewers will accept it. Also, you may be

Xcode 5 app submission issue

阅读更多关于 Xcode 5 app submission issue

问题 Some days ago I installed Xcode 5. Today I'm trying to submit an app, but during validation I'm getting this issue: "The network connection was lost". I've never had any problem with Xcode 4. My network is OK and I'm not using any proxy. What is causing this problem? 回答1: It might have been a coincidence, but like other recent xcode issues I solved this by restarting xcode. 回答2: For me the solution was to submit the app via Application Loader (downloadable directly from iTunes Connect) rather

Submit an OSX App with helper App in its bundle

阅读更多关于 Submit an OSX App with helper App in its bundle

问题 I'm really going mad with this problem! I have an app that contains a simple Helper app which manages the login item for the Main app. When I try to submit the app I get errors related to the provisioning profile and the entitlements. I'm sure that the problem is related with the Helper app because before than I added it the submission worked with no problem. At the moment the helper app is code signed and is sandboxed as the main app. The errors are : Invalid provisioning profile. The

Accessibility API stops working after sandboxing

阅读更多关于 Accessibility API stops working after sandboxing

My Mac App uses accessibility API to move an resize window (of other apps). I would like to submit my app to the MAS (Mac App Store). I have read that to submit an app to the MAS is mandatory to turn on sandboxing. When I turn on the sandboxing my code can´t find the focused window through the accessibility API (always return NULL). The question is: the accessibility API can´t be used with sandboxing? I notice that there are applications in the Mac App Store that uses accessibility API, is not mandatory sandboxing by now? Thanks in advance. Dominic Tancredi First, by March June, 2012, all Apps

Cannot test in-app purchases in Xcode 9 for macOS app

阅读更多关于 Cannot test in-app purchases in Xcode 9 for macOS app

问题 As of the release of iOS11 it has been a pain (if not impossible) testing in-app purchases. While I've found a great workaround for testing on iOS here: https://stackoverflow.com/a/46467498/4514671 I could not find anything for macOS apps. 回答1: So here is what I did that kind of does the same as with the iOS workaround: In the App Store app Sign Out of your account (Store/Sign Out) In iTunes Connect create a brand new Tester Restart your computer Open your Xcode project Build & run Click on

Can't validate and submit an App to the Mac App Store

阅读更多关于 Can't validate and submit an App to the Mac App Store

问题 I've done codesigning and submitting for iOS apps countless times. This time it struck me with the Mac App Store. I'm repeatedly getting the same error message: "My Name" is a valid identity. However, you do not have the associated package identity. I've recognized this 2 topics here on stack overflow: mas-code-signing-identity-private-key and mac-app-package-identity-not-installed Nothing inside there solved the problem for me. Thats how I (most reliably) reproduce this message: I clean up

Mac App Store: Giving up 32 bit support in favor for ARC, will existing users of 32 bit version see an update message?

阅读更多关于 Mac App Store: Giving up 32 bit support in favor for ARC, will existing users of 32 bit version see an update message?

I'm considering dropping 32-bit support for in favor for Automatic Reference Counting (which is only supported for 64 bit binaries). I'd like to avoid these two scenarios with the Mac App Store: For a user of an old 32-bit Mac : who did purchase the previous version with 32-bit support: Will they see an update message for the app in the Mac App Store? If so, the (now 64 bit only) update would not work for him/her. who has not purchased the app before: will they be able to purchase the app although it will not run on their system? ARC 64 bit only: http://developer.apple.com/library/mac/

Turning Entitlements on in Xcode Prevents Bare Bones App From Launching

阅读更多关于 Turning Entitlements on in Xcode Prevents Bare Bones App From Launching

I created a basic application in Xcode 4.2. Very simple application, I have not changed a single thing. Push run, and you get the standard base application window. If I turn entitlements on for my target and hit run, I don't get any debugger errors, but the window never comes up. I checked the logs with Console.app and got the following: First error I get: taskgated: killed com.alsbury.EntitlementsTest[pid 15903] because its use of the com.apple.developer.ubiquity-container-identifiers entitlement is not allowed After removing the iCloud Containers "com.alsbury.EntitlementsTest" I get this