I'm trying to install .mobileconfig file that was created through IPCU.
but when I click on an attached .mobileconfig file in mail.
It occured error message as "invalid profile".
what is problem ?
if the certificate is problem, please let us know how to make.
Below is the procedure I created the certificate.
in keychain, After navigate Keychain Access/Certifiate Assistant/Certificate generate,
I have generated Certificate. and exported .p12 file
.p12 file is used to Credentials setting in IPCU
You could be having any number of problems, but the one I've seen most often is that you're trying to install an encrypted profile and the device can't find the appropriate private key (which must be on the device prior to receiving the profile, and is required for decryption).
Your best bet is to get more information on the problem, which you can do by connecting the device to your Mac or PC, selecting its entry in iPCU (in the left-hand column—the entry that only shows-up once you connect the device) and clicking on the Console tab. This will give you access to the device's system log file, which generally contains a lot more info on what the real issue is.
The process you used to create the certificate seems reasonable enough and isn't likely the reason you're getting the error; I couldn't say much more than that without knowing what you're using the certificate for.
Did you sign the mobileconfig file? If yes, have you tried not to sign it?
Usually this error message pops up if you are trying to download iOS from macOS. So tap that same link from an iPad instead of on macOS, or choose the iTunes-based download method (iOS Restore Images), and upgrade from iTunes.
https://forums.developer.apple.com/message/234381#234381
Related
I have a xcode project that I would like to distribute to collegues of mine, I have therefore added all my collegues UDID in the devices section of the provisioning portal, I then downloaded the distribute and the Ad hoc provisioning files and clicked on them so that they came in to my organazizer. I then used them in xcode and selected "build-archive", I then followed this guide http://gknops.github.com/adHocGenerate/ to make a wireless app distribution. And uploaded the provisiong file, plist file and the ipa file. But when I try to install the app using the link in my html file it start to install but fail with this message " "Appnamexxxx" could not be installed right now". I dont know what I'm doing wrong and the error I get doesn't tell me anything...
I found the reason why it didn't work. I had entered the UDID of all the devices in the provisioning portal, but I didn't check that they where supposed to be used with that profile. I thought that if I entered UDID they where automatically selected to be used with the profile, this I found out by pure luck when trying to find the reason for this in the portal. So one have to select the provisionig and choose edit, then you have the reason to check/uncheck the UDID's you want in that profile. Hope this can help others too.
Hello there try to use betabuilder.http://www.hanchorllc.com/2010/08/24/introducing-ios-beta-builder/
Greetings,
I'm in the progress of writing a web server script that lets you create custom iOS apps (basically exchanging logos and a few other things). The web server customizes a previously uploaded "shell" .ipa and re-zips the whole container to send it to the user's browser. That is: we customize a previously uploaded .ipa on the web server and let the user download it for submission to the App Store.
The next step would be to re-codesign the whole .ipa - because we changed the .IPA contents and the user must use his own signing identity - so that he can actually upload it to the App Store.
From what I understand, there is a "CodeResources" file which contains some kind of hash for each resource file in the bundle, and the executable contains some kind of embedded signature as well. To generate these, you'd have to use the "codesign" utility on the user's computer, then use Application Loader to submit it to the App Store. Correct so far?
What I'm trying to find out is:
Is there a way to codesign the .ipa on the server (with having the user upload his certificate beforehand), so that he does not have any extra work to do?
If 1) is not possible, is there some kind of tool that allows to re-codesign the .ipa without much hassle? Xcode seems to require some project setup work to do just a bit of code signing - if possible at all.
Are there any alternative ways to codesign the .ipa files for the user - possibly without having to manually do it by hand?
Thanks in advance!
Xcode uses the codesign command line utility to create the CodeResources folder and the digital signature, you can invoke it yourself to sign an app bundle outside of Xcode. You could probably automate this on a server if the server was running Mac OS X; if you're really clever you might be able to figure out how to create the signature yourself using openssl (the signing certificates, etc. are all standard stuff). Or, if you can count on the user having the dev tools installed, provide them with an app that automates the signing for them.
Here's a blog entry describing some of the process (though the use case is a little different).
I don't like to answer my own question, but I want to close this after so long.
We ended up using Xcode's targets and schemes to ease up the generation of many different apps. Since we have a reasonable number of app variants, this seems to be OK for now.
Code signing is a mess and Apple constantly changes the technical process behind it - so it's a moving target and requires a lot of hacking and trial-and-error work.
I am trying to upload my first iOS app to iTunes Connect, but I am unable to do this because every time I try to upload it, I receive the following error from Application Loader:
The binary you uploaded was invalid.
The signature was invalid, or it was
not signed with an Apple submission
certificate
I have followed the instructions on the Apple website to the best of my ability. I have noticed that the .mobileprovision file that should be in my built .app file is missing - does anyone know what would cause this particular part of the problem to happen? I suspect it could be the root cause.
Moreover, does anyone have any other suggestions as to how I might correct this issue?
on the agent account in developer.apple.com
You must create a distribution certificate
You must also create a Distribution Provisioning Profile.
Download both of these and drag them onto xcode.
In the target info for your project you need to go to the code signing section and make sure you have selected your distribution profile.
Another thing you may need to do is create an entitlements file, declare this under 'code signing entitlements' as described on the apple page here
http://developer.apple.com/iphone/manage/distribution/index.action
I tried to upload my iPhone application to the App store, but received the following error: The binary you uploaded was invalid. The icon file must be in .png format.
The icon file IS in .png format, size 57x57, so assumed it is a bug and tried to upload with Application Uploader, when I got another error:
Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate.
I followed every single step, and it is not working... it is driving me crazy! Please advise what should I do!
First, check that the icon file is in .png format, rather than .PNG format.
Second, take some deep breaths, look out a window for a few minutes, and then go back over the steps to upload your iPhone application.
Many people were confusing (like me) modifying the code signing property of XCode.
You must ensure that your code signing identity property start with
iPhone Distribution : Developer Name
instead of
iPhone Developer : Developer Name
PS : If you have no option start with iPhone distribution, you didn't get production certificate yet.
Since you haven't mentioned anything regarding the fact that you did sign the code, I'm going to assume you didn't.
You'll need to get your application code signed in order for it to be accepted, so that the phone knows it's from a trusted developer, and not just a virus someone has uploaded.
Do you have a code signing certificate?
Finally got MGTwitterEngine stuff to
compile (by setting the Header Search Paths to /usr/include/libxml2 iphoneos3.0/usr/lib/libxml2)
AND link (by removing the Twitter LibXML Parsers code and assigning a weak role to libxml2.2.dylib in Targets: Link Binary With Libraries).
But when I do a Build and Go to the iPhone (not the simulator), I get this error:
"This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature)."
I have followed the official Apple Developer process of getting a certificate and provisioning, etc. Obviously, I did something wrong somewhere. Has anyone come across this problem or have any ideas on how to solve it?
Things to check:
In Keychain Access, make sure you have a code sign identity (public and private keys and a certificate titled "iPhone Developer: Your Name"
In your Info.plist, make sure your Bundle Identifier matches your App ID that you created in the dev portal
Make sure you installed the .mobileprovision (from Terminal> open x.mobileprovision)
In the dev portal, make sure your provisioning profile has your certificate, your App ID, and your device all enabled. If it doesn't, fix that and re-download and re-install your provisioning profile.
Follow the instructions very carefully when creating your Certificate. One time, in Keychain Access, when I went to Request a Certificate, I had something else selected in the list panel and so it created the wrong kind of certificate. Make sure nothing in the list is selected when you do this part.
Restarting Xcode may also work... (Work for me couple of times)
Troy It looks like the issue is you don't have a keypair that is tied to the provisioning profile installed. It's tough to tell for sure but that is my best guess.
If that is the case, I've been working in a similar situation - what you need is to either generate a private key using the iphone development portal under the same account your boss used and then add that new key to the provisioning profile you are building with.
OR
You can get your boss to export the key he generated when he created the provisioning profile - he can export it from keychain and give it a password that will allow you to install it but protect it from anyone else installing it.
I guess the fifth time's the charm. I basically deleted the certificate and the provisioning file, etc., and started completely over. Viola! Now for those pesky memory leaks! :-) Oh, Java, wherefore art thou, Java? (and your majic garbage collection!)
One of the things that I tried and worked for me was to reset the keychain access
http://support.apple.com/kb/TS1544