We have some external IOS app developers who have made a app for IOS (IPA package). They have send the IPA file to me, and they have signed it with their own developer certificate - and say that we must sign it with our own, before we can deploy it.
Should we as company just sign up for a developer app and then re-sign it or what must be used ? It must be noticed, the App must not be on "app store". It is a local company app that we want to deploy to company phones etc, so outside App store
Another note. I tried to put the Ipa on a phone through apple configurator 2. It install, but afterwards the icon stay "grey" - and when trying to click on it, the error comes that the application cannot be installed. Must the app not work through apple configurationer with manual installation ? - or has this also something to do with the developer signing etc ?
Sorry - but where is the log file on an ipod, where the installation comes up with the error.
I have now got access to our apple enterprise that we already have. But from there, how I sign the Ipa file with the certificates I cannot find any where ?
Related
I am submitting an app made in unity to the Mac app store currently, using application loader 3.0 to submit my build to iTunes connect. I was just wondering if in order to do this I am required to use/embed a Mac Provisioning Profile (Distribution) as I was told I had to but there is no mention of this in the unity docs concerning how to upload one's app to the mac app store. So my question would be if I would need to have a Mac Provisioning Profile (Distribution) and if so how would I implement it.
No, you only require the app to be signed with the 3rd party developer certificate.
The provisioning file is only needed for local testing.
This is somewhat confusing because the same process for the iOS app store does require the inclusion of a distribution provisioning files.
Assuming you have now created a .app, you must sign the .app package and all other binaries if your app relies on third party packages.
It will look like this:
codesign -f -s "3rd Party Mac Developer Application: YOUR NAME (TEAM ID)" --entitlements "entitlements.plist" "YourPackage.app"
And the same for other binaries inside the app.
I signed up for TestFlight.
Then I followed all steps in this tutorial:
But Xcode throws this warning:
Application failed codesign verification. The signature was invalid,
contains disallowed entitlements, or it was not signed with an iPhone
Distribution Certificate. (-19011)
It smells like there is a lot more work to do than what they wrote in the tutorial.
Is there a complete tutorial which walks through every step without stepping over anything?
And do I need to add the SDK even for simple beta tests?
(Edit: No, SDK is not needed!)
Start with logging into the Provisioning Portal, and adding a test device or two, under Devices. Then go to Provisioning and create a new one for the appID you are working on and add those devices.
Back to Xcode and use the Organizer:Devices:Provisioning Profiles to download (refresh) the Provisioning Profile. Set your project's Debug scheme's signing to use that developer profile. You should then be able to build and then archive. Once archived, do an ad hoc distribution and save off that file to the desktop.
Go to your account on TestFlightApp.com and press the Upload Build button. Drop the file you saved on your desktop, into the Build upload area. TestFlightApp will give you errors if the app wasn't bundled for adhoc or signed properly.
Now, here is where TestFlightApp.com will save you work. Send out invites to friends from within TestFlightApp.com. TestFlightApp.com will manage notifying them and as they create an account, it will also help them find their UDIDs. These UDID's can be batched up and later downloaded by you and re-uploaded to the Apple Provisioning Center, into your devices section.
You then use Xcode to refresh your profiles, and rebuild the app, archive, and upload to testflightapp. Then you can select which one of your testers will get to see this build and what message they should be sent. Your testers will not have to figure out how to download the files and install them using iTunes or other app, they merely press the install button.
Believe me, while it is still a bit of work, it is so much better than not using TestFlightApp.com, especially if your users are not very savvy about app installation. In the future, you can use the TestFLight SDK to gather crash reports and usage information for your debug builds.
See the following for some more info: TestFlight beta-testing iOS app
I am university student, and i received from school an invitation to apple developer which i created an account and joined the group. I downloaded and installed the "WWDR intermediate certificate" and installed it, also noticed that they added my device in the provisioning profile.
From here I am lost, were I am not sure what is the next steps I should do
Login to the Member Center
Go to the provisioning portal
Create a developer certificate (different from a distribution cert, which you'll need for AppStore release)
Create an App ID (and add a device, if you're doing an ad hoc app)
Create, download, and install a provisioning profile
Plug your iPhone into your Mac
Build your Xcode project for the device (instead of for the simulator)
In the developer portal you should:
Enter your app and give it a name.
Add the app to a provisioning file.
Download the provisioning file
Drag that file into Xcode.
In the organizer-window in Xcode - add the provisioning file to your phone. This might not be necessary since Xcode can automatically download a team provisioning file.
That was from the top of my head. Try search for a guide or tutorial for it, there's plenty of them :)
I am developing an app for iPhone. How can I test this app on my device?
What are the procedures to follow? Please give information regarding this problem.
Deploying iPhone Apps to Real Devices
http://mobiforge.com/developing/story/deploying-iphone-apps-real-devices
In brief:
Sign up for the iPhone Developer Program
Obtain an iPhone Development Certificate
Generate a Certificate Signing Request
Generate, download and install your provisioning profile
Download and install your Development Certificate
Deploy your iPhone application.
Things you will need are
your private key.
your provisioning profile (with the UUID of your device added).
go to project settings and change code signing entity to your
distribution profile.
then you can build and run after connecting your device.
1) Open Xcode,
2) Go to Active SDK, and select the OS version running on your test device (viewable by going to Settings->General->About on the device).
3) With your project open, click on "Build and Run" (or press Command-R) to run the project, which will prompt you to allow access to your keychain.
4) Once deployed, the app will run automatically.
Distribution
First of all, to run the app on your phisical device you must enroll to the apple developer program.
Second, generate a developer certificate and download it. Then, import the certificate into Xcode and here you go.
There are some steps you need to follow to test your app on your personal iPhone. Below you can find all the steps:
Creat MAC certificate at first step.
Second step is to upload that certificate to developer account.
Now you should open developer account at
http://www.developer.apple.com
You can now find an option for device id in your developer account on
left side.
Now you should register your iphone device.
It is time to create your unique identifier on developer account
Download your certificate and install it on xcode organize
Now open your project embed your unique identifier in your project.
These steps can be beneficial for all software testing gusy involved in mobile application testing.
I have developed a number of apps using MonoTouch, and been using the emulator for the iPhone, now I need to deploy me application to my iPhone for further testing.
I have purchased the iPhone SDK from Apple, but I can't find how to deploy and activate the MonoTouch application to my iPhone.
Any pointers please?
As has been already stated you obviously need the paid version of MonoTouch and the iPhone SDK. Once you have those sorted you need to create a developer certificate in the iPhone developer portal, download it to your dev machine and add it into your keychain.
Once you have done that you must create a provisioning profile for your physical device, which again you do through the developer portal. Once you have the provisioning profile, download that to your machine, and add it to the iPhone via the Organiser app in XCode.
Then fire up MonoDevelop, and if it's all gone to plan then you should have the option of deploying the build to your iPhone. You can check that MonoDevelop has correctly detected your certs by opening up the Project Options window and under the Build section and under iPhone Bundle Signing, you should see your developer cert and provisioning profile.
Full details of the steps required on the Apple iPhone Dev Site
Here are the MonoTouch docs on building for distribution
http://monotouch.net/Documentation/Building_for_Distribution
It is my understanding that you have to have the Monotouch deployment license from Novell to deploy to a device.
According to your statement:
When I compile I get: "No Valid iPhone code signing keys found in
keychain.
This is actually a Xcode question more then a Monotouch one;
The message indicates that your keychain does not provide the signing keys used to generate the certificates and provisioning profiles.
If you follow apple's steps on generating certificate(request), followed by profiles they will also state you might want to export your private key (p13 file) and keep it somewhere safe.
If you move to another laptop for instance, you will need to import that key again to make the machine a valid one.
If something went wrong (ie: you accidentally removed your private key, ..) this message will be shown since there is no way for Xcode to verify that the profiles are being used on a valid machine.
Go to this instruction page (apple account credentials needed) to check if the steps have been followed and check in the Keychain access app on your mac if under My Certificates you see a developer certificate and - if you unfold it - you can see the private key as a child node.