Install error (traced to No such file or directory when trying to find the developer profile)

I have been using Titanium for quite some time now, so I know my way around certificates/profiles and the process of deploying the app on the phone. With 1.4.1.1 (on SDK 4.1), I get the 'Install error' message when trying to run on the iPhone. I traced the error in the build.log to:

Exception detected in script: Traceback (most recent call last): File "/Library/Application Support/Titanium/mobilesdk/osx/1.4.1.1/iphone/builder.py", line 524, in main provisioning_profile = read_provisioning_profile(pp,o) File "/Library/Application Support/Titanium/mobilesdk/osx/1.4.1.1/iphone/builder.py", line 171, in read_provisioning_profile f = open(f,'rb').read() IOError: [Errno 2] No such file or directory: u'/Users/jace/Library/MobileDevice/Provisioning Profiles/D142A6D3-5CC4-4F39-8B93-7CCF687F63A3.mobileprovision'

I had a look in that directory, and of course the file it's looking for is not there. Why is this happening?

thanks

Me and most of my friends have the same problem. I solved it by copying the .mobileprovision file and renaming it to the name specified in the error log. So, in this case, copy your .mobileprovision file, put it in Users/jace/Library/MobileDevice/Provisioning Profiles/ and rename it to D142A6D3-5CC4-4F39-8B93-7CCF687F63A3.mobileprovision. This works.

If the folder doesn't exist, create it manually.

Is there an easier way to solve this problem? Anyone? :P

Thanks!

EDIT: Drag your mobileprovision file to Xcode, or double-click it before installing to iTunes.

Yes, I managed to get around it. All you have to do is go to: HOMEDIR/Library/MobileDevice/Provisioning Profiles and delete all profiles. Then, simply reimport your provisioning file in Titanium (after deleting it from the Titanium GUI as well) and build for the device. If you keep the finder window open you will see that a new copy of the provisioning file will be created. It happens to me from time to time and this solution always works!

I am getting this same error. None of the things suggested above are helping.. Thoughts?

Worked for me. Thanks.