OSX won't run my app due to "App is from unidentified developer". On Ubuntu and Win 8 it runs with no problems. It's a runnable jar created with Eclipse. How can I prepare the jar so that it can run normally with OSX? I can't relax the security setting becuase I am not admin of the target platform.
Apple Identified Developer
To sign your application as an Apple-Identified Developer you will have to enroll yourself or company in the Apple Developer Program. Once enrolled you will be granted several different types of certificates which can be used to codesign applications you distribute, whether within the Mac AppStore or outside of it.
Unidentified Developer
If you'd rather not join the Apple Developer Program then you would need to inform users of your application to allow it to run through the Gatekeeper settings from their System Preferences Security Panel, or to override the security as they launch the application (only required once).
Related
Things have been changing in the Mac Appstore.
As at 10.15.5, all apps, regardless of distribution via AppStore
or outside the AppStore, will need to be notarised. I dont
believe that's true of apps that are shared with your testers
via a profile that specifically lists their device.
I'm struggling to get the right combination of cert type and profile to
be able to distribute my app to my testers to run on their machines.
I have a company and that company has an apple account "Acme Widgets" and
the account holder is "admin#acmewidgets.com".
I have a personal apple dev account too, and I've added myself into the company as an admin.
So when I login to developer.apple.com as myself, I can switch between my
person account "Paul XYZ" and my company account "Acme Widgets".
I have an app developed using Xamarin (visual studio) with a Mac and iOS versions.
I can create a Debug and release versions of my iOS app, no problem. Upload it to the App Store and testers can get it with TestFlight.
Its the mac side that is causing problems...
I can create a Debug version of the mac app, and leave it unsigned.
Or I can sign it with a company developer ID and a profile that includes my Mac.
These run on my mac fine.
But release is causing problems. I want to create a release build that I can
share with my small set of testers. Therefore I think I need to use
the company "developer ID certificate", and a "MacOS development profile" that includes
their devices. But that wont run - I just get code signing errors.
I'm missing something obvious.
Can someone point me towards the type of cert (personal, personal in team or
team/company), and the type of profile I need to share a release version
with my testers?
Many thanks.
Paul
i have generated the .ipa file and trying to add in any iphone device but its not adding.
the error is showing like:- couldnot install(in xcode).
i tried with apple configurator 2:- in this scenario app is installing a bit just assume
75% and after that the app icon is getting grayed out and clicking on that app is giving
popup as :- could not install please try later.
somewhere i saw that you have to allow from your device to trust this app, location is like :- settings > general > profile&management > you will find your profile here for new app installing.i didn't get any profile there.
FYI
i am using free developer account and created the xamarin app from windows and building it through mac, the xcode version is 9.4 beta and i also tried to override with xcode version 11.3.
i am not getting whether i am missing something or messed up with xcode versioning.
i am using free developer account and created the xamarin app from windows and building it through mac...
If using a free apple developer account , you can not install a .ipa file to iOS Device .This is limited by Apple.
About IPA Support in Xamarin.iOS , you will see there are two uses as follow :
Ad Hoc Testing — An iOS application can be deployed to up to 100 users (identified by specific iOS device UUIDs) for Alpha and Beta testing purposes. See our Provisioning an iOS Device for Development documentation for detailed information on adding test iOS devices to your Apple developer account, and the Ad-Hoc guide, for more information on how to distribute in this way.
In House / Enterprise Deployment — An iOS application can be deployed internally, within a company, which requires membership of Apple's Developer Enterprise program. More information on In House Distribution is detailed in the In House Distribution guide.
In either case, an IPA package (a special type of zip file) must be created and digitally signed with the correct Distribution Provisioning Profile.
If using a free provisioning , there is a Limitation as follow :
Access to iTunes Connect is limited and therefore services such as publishing to the App Store and TestFlight are unavailable to developers provisioning their applications freely. An Apple Developer Account (Enterprise or Personal) is required to distribute via Ad Hoc and In-House means.
Therefore , if need to add .ipa file in iphone device , you should use a paid Apple Developer Program account.
Some users of my Qt Application are reporting some issues about antivirus (Windows) and "unknown developer" (OS X).
In some cases, on Windows, the antivirus is blocking the application or showing a message that the application can be dangerous. What can I do to my Qt Application be "trustworthy" to the antivirus?
On OS X, when the user tries to run the application, the system shows a message about "unknown developer". What can I do to not show this message?
Unfortunately, I can not give more details about the problems because I could not replicate the problems on my machine. I am just asking based on the problems reported by the users.
In macOS - you need to sign the app using a developer certificate.
You need a developer account for signing apps.
Users will still see a message after signing the app if it is not distributed via the AppStore, but unlike the 'unknown developer' message that only has a 'close' button, the user will have an option to open the app once it's signed.
I can only assume the same applies to windows (less restrictive if I remember correctly) - you probably need to sign the app using a certificate obtained from Microsoft.
You will not see this message when running on your own machine, unless you're using an archived and exported version of your app.
In order to fully test an app on your own machine - create a non administrative user (useful for testing how the app works for non admin users, regardless of signing issues) on your local machine and test the app using the newly created account.
Do not compile or debug the app using the new account, use that account just for testing.
I have installed new inHouse provisioning profiles, however when I archive my build in Xcode, I am presented with a message saying the iOS development team is missing. I have xcode 6.4.
I know that you are able to build and sign an app if you don't have a developer team membership in Xcode.
Anyone know what is wrong?
Also another strange thing when I go into keychain to check if profiles and keys are there, they are not stored under the "Login" section like other profiles, but in "System". Is this ok?
Thanks
In order to archive your build (either for the App Store or Adhoc) it must be codesigned by Xcode. This requires a signing identity. Signing identities are only obtainable through the developer console at http://developer.apple.com/ and requires being a member of the apple developer program to access.
Sorry to break the news but without a developer membership you won't be able to archive your app for a device, but run it in the simulator only.
I have a Cocoa Mac App that I don't know if it will on the Mac AppStore.
The application is still in development, and I want few persons to be able to launch it on their devices while the app gets new features.
The situation is the following :
I have a Mac Developer Certificate
Devices are registered in the Mac Member Center.
Every time they launch the app, GateKeeper complain the app doesn't come from the Mac AppStore, nor is provided by a identified developer, no matter if I sign the app or not.
So I tried to sign it and a provisioning profile is embedded into the app. If I don't sign it nothing embedded.
I should mention that the app has a Spotlight importer and QuickLook generator bundled into it.
I didn't find any clear explanation on how to resolve this issue in the Apple documentation, and most (if not all) blog posts, or articles on the Internet are about iPhone apps, not Mac ones (the process/requirements seems to be different on the two platforms).
The documentation is unclear on if all testers should be team members (which seems crazy because some of them aren't developers and don't have Xcode installed).
Can someone provide a clear step-by-step explanation on how to do that ?
Or maybe a article/blog post link or tips ?
Edit :
Here are screenshots of the app bundle structure and plug-in structure :
Everything seems to be right.
The way I obtained that is : I didn't set "Code Signing Identity" build setting, but rather archived the app, and exported it specifying code signing identity at that time.
Edit :
More and more curious, when I run codesign command in the terminal, codesign -vvv MyApp.app, the output tends to suggests that all is rightly done :
MyApp.app: valid on disk
MyApp.app: satisfies its Designated Requirement
Interpreting this question as essentially:
"how do I beta test Mac App Store apps" ?
Apple hasn't yet published an official workflow in the App Distribution Guide, but the following process works:
Tester sends "System Information utility > Hardware tab > Hardware UUID" to developer
Developer updates dev provisioning profile to include the hardware UUID
Developer uses Xcode Organizer Archives tab, Distribute > "Save as Mac Application", then select the updated development signing identity.
Developer sends newly built app to the tester
Note: The development identities have yellow caution ! icons during the re-signing process but they can still be used.
Not only does this avoid the GateKeeper prompt, but the development provisioning profile is also needed for any store technologies you might be using to work during testing, e.g. iCloud, GameCenter, etc.