So I haven't opened my Xcode project in a while and haven't even looked at any code in months. Now after banging my head through the wall, still no App money in my pockets, and losing my mind over some stupid apple program errors I remember why...
The full error is:
"App installation failed - A valid provisioning profile for this executable was not found"
Now I know this error has been posted here multiple times and each has a set of answers that miraculously has helped some people, some of which are the most insane answers that are for particular events such as one guy's device date was set in future...uhh
Anyway's, after 2 days of trying every single "Answer" for this error and over an hour on the phone and letting an unexperienced Apple supporter take over my screen and getting absolutely nowhere I need some serious professional help from who else but stack overflow geniuses, right? Also I'll mention Apple does its fair share of going to this forum when they are clueless. Ha! Who would of thought,oh ya, probably all of us.
Continuing on here... To me a lot of these answers are too complex when Its simple to me. Its saying my device doesn't have the provisioning profile, which checking in the Devices window and right clicking to show the device's provisioning profiles, there are none obviously. When of course there should be. Now there is a button to manually install the provisioning profile. NOW, ONLY IF THIS WORKED! it doesn't and that in itself is something also listed on here and for me directly responds to my error.. (Just Search: provisioning profiles won't install on device)
http://support.hockeyapp.net/kb/client-integration-ios-mac-os-x/known-issues-with-ios#manual-installation-of-provisioning-profiles
This above link is a site that is the only thing that is agreeing something else is wrong here and would also explain what I already was sensing. This project ran fine last I ran it when my device was on iOS 7. Also another device thats on iOS 6 gets the provisioning profiles. So clearly iOS 8 is bugged like it always has been and I don't know what to do about it cause Apple makes horrible buggy updates to products and doesn't let you downgrade.
So please, does anyone have any idea how to get around this?
Bonus Question: Why are we always "getting around" super simple errors that never get fixed by Apple?
Related
I am doing an Update to my app. I added a Watch Extension and I had many errors regarding provisioning profiles and so on when trying to submit the binary. However, I somehow managed to get it to work and submitted my update. Today I was rejected because of some small issue. I quickly changed it and now I am trying since hours to resubmit, but now I am getting this error:
CFBundleIdentifier Collision - The Info.plist CFBundleIdentifier value
'com.mentalfaculty.Ensembles' of 'MyAppName.app/Ensembles.bundle'
is already in use by another application.
I don t really understand what is wrong. The thing is, I did just fixed a really small thing, besides this I didn t change anything, I used same provisioning profiles since some days ago when I was able to submit, so I really don t get the problem what has changed from my last submission. I also don t understand this error message: what other application?
"Ensembles" is a framework that does Core Data iCloud Sync. I am using it since two App versions before and never changed something. I just followed the install instructions, and I had to integrate that Ensembles project in my own project. So this framework is kinda a project within my project. It has it s own info.plist. Obviously that error has something to do with it, but since I am not really an expert in these things, I m afraid to change something.
So why was I able to submit two working and approved updates, was able to submit one update binary (that was rejected) and now getting this error all the time although I really didn t change anything and did the same steps when I was able to submit some days ago?
Would be really thankful for any help here !
Thanks !
I am the developer of Ensembles, and started hearing of this error a few days ago. It seems something has changed on Apple's servers, and even bundles that are just Resources, like Ensembles.bundle, must have a unique identifier. It is not clear if this is a new policy, or an overzealous script on their server.
In any case, the solution is reasonably straightforward: you can just go into Ensembles.bundle and change the bundle identifier to something unique of your own. Eg. com.mycompany.ensembles.bundle
Update
Apple seem to have resolved this issue server side.
Thanks Drew for your help again, already helped me with another Ensembles related question in another thread here! Your framework is really great, so easy to implement and it takes away all that iCloud integration pain right out the box. If you want to see your work in action, check my profile, there is a link to my app. Mentioned your work of course in its settings bundle.
Last night I ended up doing exactly that, changing the Bundle Identifier in the Ensembles framework. After that iTunes Connect accepted my built. I was just afraid of changing something there and screw all up, but at least from my tests on my devices, it still seems to work like before... Strange because I uploaded a built just 10 days ago without the need of changing the Bundle Identifier, so Apple must have changed something really recently.
So for others having that problem, what I did:
Ensembles iOS.xcodeproj - Ensembles Ressources iOS - Ensembles Ressources iOS-ibfo.plist
I changed the Bundle identifier from
com.mentalfaculty.${PRODUCT_NAME:rfc1034identifier}
to
com.mentalfaculty.MyCompanyName.${PRODUCT_NAME:rfc1034identifier}
Thanks !
I dont know why, how and when but this is the situation today in my developer console:
Now I need to update my application but Im scared that because of this situation, my app won't work anymore like it should (for example push notifications).
Can anybody tell me what's going on, if this is a problem with my update, if I must fix it, or whatever...?
Thank you
It's not an issue. Xcode has a tendency to invalidate lots of profiles when you click "Fix" sometimes when there is an issue. You can go in to the profiles, edit them and recreate them without any adverse effects.
You can use Sigh which seems a good way of managing your profiles: https://github.com/KrauseFx/sigh
I realize this question comes up a lot, but there is no one solution that has seemed to work for anyone.
I am working on developing an app for iOS and recently had to transfer my app to another developer account. My first account was an individual account where I was "Agent," and now the new account (corporate I think) has me listed as "Agent."
I created the certificates like I have always done, downloaded them, and placed them in my keychain. Everything said it was in order. I then created the app ID and re-entered all of the devices into the devices column. I moved on to the provisioning profiles, and again everything worked well. I downloaded them and imported them into Xcode, and when I go under settings and look under the account, it all looks in order.
Then when I attempt to build in corona, it tells me "Certificate Not Installed." Even though I had created the certificate on that device.
A possibility is that having 2 apple dev accounts signed in at once was confusing, so I logged out of my other, and, not surprisingly lost my ability to build for those either. I could still not build for iOS.
I have tried restarting my computer several times, and deleting everything and starting from scratch. I have tried creating the certificates a variety of ways and billions of combinations. I even tried using my other computer - although it also had dev set up for my other account.
Am I missing something crucial here? I don't have another computer to start over on if that is what it takes, but I guess I could clear one...
I greatly appreciate any suggestions!!
More specifically, for Starter and Basic subscribers, on OS-X you will need to download a new latest public build (2014.2393a). For Pro and Enterprise subscribers, you will need 2014.2405 or later.
Starter and Basic subscribers may have to add something to their build.settings for now due to another change Apple instituted this week. See: http://coronalabs.com/blog/2014/08/21/ios-building-issue
After some more hours of digging, I finally found a solution. Apparently apple changed some things in their newest releases, specific to their provisioning profiles and something in Xcode.
Corona Forums had this thread that solved ALL of my problems: http://forums.coronalabs.com/topic/50226-certificate-not-installed-cant-build-for-ios/page-2#entry260678
To summarize the forum - you need to install a new build of corona that solves the problem: https://developer.coronalabs.com/downloads/coronasdk
I hope my struggles have helped someone :)
Not the most bright question, but I really need an answer.
I created an iPhone app with a friend. I did the first 100 hours of the development (by myself) and he did the rest (sometimes I'd help him debug in class). He then took it over completely; finished it and uploaded it to the app store (no idea how that process works). Since we don't know git well enough I emailed him the code. A few days ago I asked him the most recent version of the code back, so he mailed it to me in a zip file and now I can't build the app.
What I want to do is build and run the app in the simulator.
Instead I get the following error:
Even the play button doesn't display anything.
My friend also has no idea why this error occurs. My guess is that he barely knew enough to upload everything to the app store. Also I don't have a developer account, because the person who we are building this app for has it. He gave it to my friend, but my friend doesn't want to give it to me. And the person who has the developer account is not responding.
What should I do? I "just" want to build and run it on my macbook (I know, it probably isn't that easy).
What do I need to know?
So my target was the following at first. This was my only option. Clicking at it did not help, it only showed this thing as an option.
Then after the comment of Nitin I poked around for a bit (for the 10000th time). I did this by clicking on the gear icon which has the option "Manage Schemes..."
I don't know what a scheme is and I remembered that I never saw this menu box before. For fun I clicked on "Autocreate Schemes Now". I got this as a result.
My guess is that it was a new target to build at, and indeed it was.
I can now build and run my project without signing.
Thanks for the comment, it led me to the answer while clicking around once again :)
I need to install a flash file using adobe air for ios on my iPhone.
I know of this link here that had a similar problem with the same error message
air-for-ios-device-error-please-check-if-there-is-enough-space-on-the-device
But here is my issue, I have created an empty document, nothing in it and created the certificates and provisional profiles in my apple developer portal and it keeps giving the message "device error: please check if there is enough space on the device"
I have over 3Gb free on my device, so I am not sure why it is saying that.
Is there anything else I need to check or do especially?
I have done direct testing and created ad0hoc files and nothing works.
Any tips would be great, in the mean time I will keep googling, but no luck as yet.
So I fixed the issue - I re-created the .p12 certificates and it worked. Not sure why it didn't the first time.
I am not sure about the moderators for the forum, but maybe this could be turned into a protected post where people can post their issues and help each other rather than creating more posts on this same topic??