I added a new application for the new Mac OS X app store and the status is "waiting for upload", but when I launch the application loader it tells me "No eligible applications were found". I have ensured I am using the correct itunesconnect login by running the setup wizard from the application loader menu, but it still tells me I do not have any eligible applications for upload. Do I use the application loader to upload Mac OS X binaries? or is that just for ios applications?
This is a step by step explanation by Apple: https://developer.apple.com/appstore/mac/resources/submission/
Otherwise use my small turtorial:
You have to add an application entry:
https://itunesconnect.apple.com
Goto "Manage Your Applications"
Then click the blue button "Add new App"
Select "Mac OS X App" (if it is not available you need to buy the membership)
Fill in all required steps
Restart the Application Loader, your App will occur.
Check also this: http://developer.apple.com/devcenter/mac/documents/submitting.html#//apple_ref/doc/uid/TP40010572-CH16-SW5
Related
I am working currently on adapting our Email application written on Xamarin iOS to run correctly on Apple Silicon M1. I have faced the following problem that I can't solve so far. The problem is that our code written for iOS that uses UIDocumentInteractionController on Apple Silicon opens "Share to" menu, also if I try to change this to Launcher.OpenAsync() call from Xamarin.Essentials it also opens "Share to" menu instead of opening the file with default application. I tried to use Launcher.OpenAsync() from Xamarin.Mac application and run it directly on Apple Silicon from VS Mac and it works as expected this way - opens file with default application. However when running from iOS application installed on Apple Silicon it always opens "share to" menu. It is a big problem for us as we need to allow user to open attachments files from our email editor. Any ideas what I can try to do to solve the problem?
So in the end I replaced our UIDocumentInteractionController with Quick Look Preview Controller which works as expected both on iPhone and iOS application running on M1.
In XCode 8.2 I have two MacOS apps under development that I will refer to as A and B. From Organizer I am able to "Export as a macOS App" for app A and run it on another mac without error. But when I do the exact same for app B the other mac displays a prompt "Sign in to use this application on this computer" and "B was purchased using the App Store on another computer...". I shouldn't have to sign in, but when I do the next result is the "Damaged" error.
Both have "Automatically manage signing" selected. I can validate both for the App Store and "Developer ID-signed".
Has anyone succeeded to run a Developer ID signed Mac App with CloudKit and with access to the Production environment, using Xcode 8 beta 3? According to this diagram of Apple it should be possible, but all my attempts lead to crashes. What are the exact steps to follow?
My attempts until now includes the use of a "Mac DirectDistribution" Provisioning Profile that points to an App ID with CloudKit enabled and with access to an iCloud Container.
My CloudKit enabled-app works perfectly with a standard App Store configuration, but I want to test it with a Production environment.
Just add the following entry to your entitlement plist and do a clean build (shift+command k). No other action is needed: (string to copy: com.apple.developer.icloud-container-environment)
After countless experiments I found the following working solution to test CloudKit on the Mac with Production data, using Xcode 7.3:
In your App project, choose Developer ID in Targets > Identity > Signing
In the Entitlements file add a new line with key "com.apple.developer.icloud-container-environment" with value "Production"
Run the App (debug modus)
Export the app to an Archive, choose Export and select "Export as a Mac Application" to produce a Developer ID-based release version.
The steps are more or less the same if you use Xcode 8, but you have the extra option to disable the App Sandbox.
For Mac the easiest way is to just after Archive click Distribute App then choose Development and click next then choose your iCloud Environment (Production/Test) and save the app wherever you want. This version will access your production iCloud.
enter image description here
enter image description here
I have a Mac App for OS X 10.10 that I am trying to create a working release build.
Not for the Mac App store "Distributing Apps Outside the Mac App
Store"
Uses "Developer ID Application" for the release code signing. Things look good in my App dev account
Created an OSX APP ID com.blah.app
Can create and verify an Archive successfully
sudo spctl --assess --verbose=4 Name.App, looks good "Name.App : accepted
source=Developer ID"
Read thru Apple "Distributing Apps Outside the Mac App Store"
Needs to be OS X 10.10 due to customer requirements
Read through everything I can find on stack overflow regarding this
matter
Can build and release iOS without a second thought, but this is my
first Mac App
I run the App and in the console I see "EXC_CRASH (Code Signature Invalid)"
Stumped ...
Gatekeeper
Macs have a "gatekeeper" feature that can be set in 3 modes in System Preferences > Security & Privacy > General > "Allow apps downloaded from:".
Which is your test system set to ?
Since you're signing using a Developer ID, it needs to be set to the 2nd or 3rd option (not just allowing the App store). [2nd option is the default on freshly installed machines]
Build for distribution outside of the app store
Builds that you create for submission to the App store cannot be run by everybody. One needs to build it specifically for that.
To quote https://developer.apple.com/library/mac/qa/qa1884/_index.html :
[...] use Xcode Organizer > Export > Export a Developer ID-signed Application. Developer ID-signed apps can be run by anyone. However, code that uses technologies only available to Mac App Store apps, such as receipt validation, iCloud, and push notifications, will not work if your app is Developer ID-signed. You might need to temporarily disable those parts of your app if you opt for the Developer ID testing approach
There was an error in the selected capabilities (red) that wasn't stopping the build, "Key chain sharing" in this case. Turned off as I didn't need it and everything works as expected
I had developer application for MAC desktop.
I would like to submit it to client for testing.
But not able to find the steps for developer distribution.
Like iphone application :- we register the UDID of the device (iphone/iPAD) and then add those in the provisioning profile and then create the ipa.
How do we create developer ipa file for mac desktop version.
please help.
I am new to mac os application
There are a couple guides about distributing Mac OS applications. "Distributing your Mac Apps" is the main entry point.
If you want to distribute your app to client just to test you can sign app with Developer ID certificate. In this case you need to investigate this certain chapter "Distributing Applications Outside the Mac App Store".
Separately you have option to export application bundle without any signing.
Short steps:
Select menu item Product->Archive
Click Export button
Select "Export as Mac Application"
Click Next and save your app