I am trying to run an app on my physical device, it starts to build onto my device then crashes due to an 'invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user.'
I have updated my iPhone and Xcode to the latest release, tried to clean the build and edit run scheme build configuration to 'Release' and tried to set my executable to 'Ask On Launch'. I searched for a Iphone Developer file on keychain and could not seem to find one but i am not sure what i am supposed to do.
Can anyone help?
The problem is that the developer is not trusted on the device. If you manually try to run the apps on the device, you will see an Untrusted Developer message.
To solve this issue on the device, go to Settings > General > Profiles or Settings > General > Device Management, depending on the device type and the iOS version. There, trust the developer and allow the apps to be run.
For newer versions on your iPhone (version 14+)
Settings > General > Device Management (In the VPN section past Date & Time section).
Then trust the device
Adding newer settings
2022 iPhone 15 variation. Load the app --> Next as below.
Settings > General >
VPN & Device Management > Developer App > Trust "Apple Development:....."
Please check the internet connection of the Testing IOS device, Signature verification fails if device isn't connected to Internet.
I had the same issue, I just
Created a new Project with the sample Hello world
Deployed it to the device - it was working
Deployed my desired app again and it started working
I hope it helps.
If nothing works, do this,
Open XCode -> Window -> Devices & Simulators.
Remove your device from that window.
Reconnect the device and you will receive the trust certificate again.
This work after upgrading to iOS 15.
on your iphone,
Settings > General > Profiles or Settings > General > Device Management
Developer app. (Click on) for trust.
In my case simply reconnecting the lightning cable did the job.
If you see this issue happen out of nowhere, one other possible source of the problem is a network outage.
Your device will periodically need to dial out to a service to validate the provisioning profile. I don't have details on how often this needs to happen but I do know this validation action happens during the app's startup. If your device can't connect to the internet or Apple is experiencing an outage, it can interrupt this process and produce this error.
You can check the status of Apple's services here:
https://developer.apple.com/system-status/
Certificates, Identifiers & Profiles is what you want to keep an eye on.
If none of the above works and you've already trusted the developer, try 4G/5G connection instead of wifi.
This problem occurs because the installed app's developer is not trusted by iOS device.
To solve this issue on the device, go to
Settings > General > VPN & Device Management
Here is the screenshot
I was about to upload an app to iTunes connect,but the application loader has been stuck at the stage of "Authenticating with the iTunes Store" and pending for almost an hour.Network is fine and I have never seen this before.Has anybody encountered this kind of issue? what is the solution?thanks in advance.
I had this problem when behind a firewall.
I got around it by editing:
/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/MacOS/itms/java/lib/net.properties
If you do not find net.properties in above mentioned path then try, as it is changed now.
/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/java/lib/net.properties
Change the line:
# https.proxyPort=443
To:
https.proxyPort=80
This enables the application to use the HTTP port for HTTPS. Worked straight away after this.
To be honest, this may not be an answer but it really worked for me.
I launched Application Loader and started submitting.
While sumbitting was going on,
I launched Organiser and select Distribution over archiver in Xcode
as well and started uploading concurrent.
They worked together and 2nd one completed the submission.
Just my experience.
I tried many solutions like using port 80 for https connection but none of the solution worked for me.
https.proxyPort=443
to
https.proxyPort=80
Whenever I face this issue, I upload application from two different instances of application loader and it works like a charm.
I have two different versions of application loader on my machine, one came with XCode4 and one came with XCode5. It always works if I upload application from two instances simultaneously.
I was quite frustrated by this - not only by the problem itself but the uncertainty till when I need to wait to call it "It won't - try again." - at which point I will quit the Application Loader app, re-package my ipa file and try again. Probably with a port change to net.properties file. But it didn't always work the same way as it did last time. So I am writing it here, mostly for the sake of myself!
I was about to just call another day thrown when this worked, almost like a charm:
1) Open file. Applications > Xcode > Contents > Applications > Application Loader > Contents > MacOS > itms > java > lib - net.properties
2) Change the line:
# https.proxyPort=<whatever>
to
https.proxyPort=80
Make sure that you do not uncomment # https.proxyHost= - just leave it as shown (commented).
3) Start Application Loader. Follow usual steps and start uploading your ipa using Send command.
4) If it seems to be getting past "“Authenticating with the iTunes Store” in reasonable time (say 10 minutes at which time my patience ran out) - you are lucky. Go sleep or hang out.
5) Launch Xcode Organizer. Select your archive and click Distribute button. It will show slanting progress lines for couple of minutes. If it doesn't stop, kill Xcode and retry.
6) After about 2 slant minutes, the blue solid progress will appear, and there flies your "Flappy Bird"...! (mine was neither Flappy nor Bird)
(Keep the Application Loader alive, just for the sake of having it around, I don't know if it's useful anymore, but I am just superstitious)
Workarounds apart, this is something Apple must fix before releasing iOS 8 or iPhone 6. Seriously. If they don't, I am not wasting my $100 next year.
(Or - will this bug be still around to prevent those "Flappy" clones from flooding the app store, forever?)
Tested with xCode 5:
In my case nor organizer or application loader worked: they got stacked in “Authenticating with the iTunes Store”.
I solved it sending the app by application Loader, and when it got to the “Authenticating with the iTunes Store” I opened the organizer and upload the app: application Loader and organizer sending the app at the same time.
It seems that something is going in my router port configuration and my computer can not receive the answer from itunes store saying that authentication was successful. Maybe the process is this way:
1- Application loader request authentication.
2- Itunes store authentication is done but application loader never receives the answer. [But it is authenticated anyway!]
3- Organizer sends the app because it is already authenticated by application loader.
I solved this problem by starting second instance of Application Loader while first instance saying "Authenticating with the App Store...". You can start second instance of Application Loader from Terminal using:
open -n -a "Application Loader"
Try use another internet connection. I have the same problem when try upload app via Wi-Fi. Nothing helps me, but when I disable Wi-Fi and try do it via EDGE on my iPhone, everything is works!
You may give a try to application uploader. Yesterday me too faced this problem and even application upload didn't work for me then I tried this:
For uploading it via XCode:
Step1: Firstly Validate your archive file by clicking on validation
button of Organiser.
Step2: Then Upload it to App Store via Oraganiser. By clicking on
distribute and then first option and so on.
it really worked for me
If validation is successful while uploading through organiser then it must be network issue. Application loader uses some specific ports including port 443. If any of those ports are blocked by your internet service provider or on your local network then application loader can stuck. Certain applications also block these ports. If you are running Skype close it. If it does not work then this solution worked for me finally. Make modifications in net.properties file. You can access this file by going to Application folder via terminal.Then move into Xcode.app with cd Xcode.app next
Contents with cd Contents next
Application Loader.app with cd Application\ Loader.app next
Contents/MaxOS/itms/java/lib
Now you find net.properties.
Now write sudo pico net.properties and add following lines in the file
https.ProxyHost=
https.ProxyPort=
https.ProxyUser=
https.ProxyPassword=
Now launch application loader to upload you ipa file and it will work like a charm.
Sometimes it is the network trick. Connecting to different network may solve this problem.
I tried both the two ways(Xcode/application uploader) at home, neither worked.
Then, I brought my macbook from home to library, it finished uploading within 3~5 minutes there(via application uploader).
Contents/MaxOS/itms/java/lib
Now you find net.properties. Edit that with your favourite text editor. Add the below lines
https.ProxyHost=
https.ProxyPort=
https.ProxyUser=
https.ProxyPassword=
You may have problem uploading through app store via xcode if you have slow internet connection, but using Application loader you can achieve the submission.
We tried lot of things which is giving in this and other posts, but it did not work.
Finally we gave the IPA file to the client to upload it via Application Loader from his end. And it worked.
So, I would strongly suggest that if your app validates fine and it still remains struck in Authentication, then rather than trying out anything, just try uploading it from totally different network in different geography.
That will save you lot of time and headaches.
All i did was duplicate my Application Loader.app in /Applications and ran both Application loaders at the same time.
Simple use this command in terminal it worked for me:
1. cd
2. ~mv .itmstransporter/.old_itmstransporter/
3. "/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
I faced similar issue today while uploading .ipa via application loader which was opened directly from spotlight. Every time it was passing all the steps but getting stuck at Authentication. (AL Version 2.9)
After dozens of failed trials, I launched Xcode and opened application loader from Xcode (AL Version 2.8) and repeated earlier step. Interestingly it failed at first checking step itself! It said it had some issue with certificate .. so followed all the steps again to get new certificates in itunesconnect and on mac.
(if some one wants.. here are good instructions with pics)
It got authenticated and the binary file uploaded fine.
I tried many things including the suggestion provided here. Once I re-login in "Application Loader" to restart the delivery. The package passed the authentication stage and start uploading. Maybe "Application Loader" needs to revalidate your authentication but can't say it loud.
This happened to me today. I shutdown my Mac and then tried the application loader after couple of hours.
It worked.
I guess it was a problem at iTunes Connect.
I had the same issue. Trying all these answers may work sometimes, but usually it takes much time and may not work at the end like in my case.
I figured out a solution which will probably work for all.
Create your .ipa file by: Product -> Arcive -> Disribute(Save for Enterprise or ...) -> Next and save .ipa at target
Xcode -> Open Developer Tool -> Application Loader -> Deliver your app -> Pick your .ipa file
Withing few minutes your app will submit to iTunes. Good luck
Charles Proxy (or any other proxy) could have this effect.
Review and accept any new terms in member center.
Best and quickest fix I found is to copy 'Application Loader' from 'Applications' folder to desktop, run both 'Application Loaders' simultaneously.
Works like charm every time :)
There is nothing wrong with server of any ports in my case. I have 9 MB of build. With good interenet speed it takes 5 minutes. I feel I got stucked. But after few minutes it uploaded successfully.
I was missing the distribution signing entity. I created and it did work.
After struggling for days with this problem the only working solution for me is to use the Application Loader with only the DAV protocol selected.
Application Loader -> Preferences -> Advanced -> Use only DAV.
The problem is due to my corporate network restrictions.
DAV uses https so it's not blocked.
Solution found here:
itunesconnect using application loader behind a firewall
open terminal and run these commands
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application
Loader.app/Contents/itms/bin/iTMSTransporter"
got it from here
Hello Friends, Do not worry about it, Simply disable the bit code option in build Settings and make build and upload.
No need to do any extra work
Try this one
I am submitting an iOS app to the App Store using Application Loader, however, it never gets past the "Sending API usage to iTunes Connect" stage. There is no error - this stage just doesn't complete.
I have verified that the Mac is connecting to the internet (I can visit websites). Also, the app is tiny (6MB) so this can't conceivably just be a long upload. I've tried leaving this for 20 minutes.
The background to this is that I developed in Flash CS5 on a Windows PC, built it for distribution there, and now on the Mac I am loading the final file into Application Loader to submit it. It verifies/validates the file just fine, but won't go beyond this point.
Any ideas anyone? Perhaps it's a network issue?
I had this problem when behind a firewall.
I got around it by going to Xcode > Contents > Applications > Application Loader > Contents > MacOS > itms > java > lib - Open net.properties with TextEdit and change the line
# https.proxyPort=443
to https.proxyPort=80. This enables the application to use the HTTP port for HTTPS. Worked straight away after this. Hope this helps.
You can solve this with a different approach using your iPhone. Disconnect ethernet internet cable connection (if you have one) and/or switch off wifi connection on your mac. Switch off your iPhone's wifi connection so G3 or G4 is active and turn on personal hotspot. Connect your iPhone with a usb cable with your computer and check in System Preferences -> Network if you're connected to internet via usb with iPhone. Start delivering your app with Application Loader program on your computer via your iPhone's internet connection. And yes you will cross the “Sending API usage to iTunes Connect” barrier and you will be able to upload the package to the iPhone store. At least I was!
If your Mac is has both a WiFi and an Ethernet connection, try turning off WiFi. That solved the problem for me (this time anyway).
I solved only rebooting mac.
I'm still searching for a less drastic solution!
I had my DNS set up to Google DNS. I removed the DNS settings and it worked for me.
Turning off iphone's wifi worked for me
Are you using Xcode Organiser > Upload to App Store or Application Loader?
I found I had the same issue when going though Xcode Organiser so tried it from the Application Loader (found within Xcodes application files) and it worked just fine. If that doesn't work there is a detailed activity log you can check to get a more detailed error.
Other things to try
- check your firewall settings, maybe temporary disable them.
- use an alternative connection, another wifi hotspot if you are on a MacBook, if not do what Oliver said and use your iPhone's cellular data.
I was connected to a VPN, disconnected and problem was solved.
I'm developing a "two-part" app, where companion apps are installed on an iOS device and an OS X computer. What happens is:
iOS device gets connected to a computer via USB
Once connected, the iOS app writes some stuff to a local file.
Now how can I get the computer to read from that file? Would this require something like Bonjour, even though it is directly connected?
Without going through iTunes and it's File Sharing mechanism or trying to mine backups (also created through syncing in iTunes), you're pretty much out of luck moving data between the iOS device and the computer via the USB connection.
Unfortunately, the only reasonable way to handle this sort of thing is via a wifi network connection between the iOS app and a service running on the Mac. Bonjour is very handy for service location in getting the Mac/iOS device together.
How to install my app in adhoc release on multiple device with the same computer/itunes, when i try to do it, itunes sync the devices..so i clean them up ...
Apple has solved your problem with an Enterprise Utility called the "iPhone Configuration Utility" which you may freely download from their information webpage here: http://support.apple.com/downloads/iPhone_Configuration_Utility_2_0_for_Mac_OS_X
Once you install this and connect a device and close iTunes (which typically launches in response to the device connection) you can easily use its simple interface to manage your adhoc provision profiles, add the device and install or remove adhoc apps directly.
I used this app months ago to put the Crash Landing demo I'd built with the SDK directly on my wife's 2.1 iPhone 3G from my desktop dev Mac without messing up her own laptop Mac iTunes sync management of her apps, music, etc. FYI: I've not tried this since the June update to v2.0 of the Utility which accompanied the release of OS 3.0. edit: I couldn't resist testing this (yes, it still works)
The only downside I noticed to this method is that the iPhone/Touch user will have to later delete the app manually on their device, as their iTunes management won't list the app in the device applications tab to be unchecked.
it should just work, as long as the mobileprovision file that you're using includes all of the devices that you're trying to use. (also assuming that all of the devices are set to sync to that one computer's iTunes library.)
If the device is jailbroken you can install sshd and copy the application directly.