When I try to validate my build using xcode 6 GM release I am getting this error.
Error : itunes store operation failed no eligible software found. Make sure this software is owned by your developer organization.
Can anybody here suggest some solution?
Probably you're using a different AppleID for iTunes Connect than for Developer Portal. You can use such a workaround:
Export archive in Organizer (Save for iOS App Store Deployment) and then use Application Loader (Xcode > Open Developer Tools > Application Loader) to upload it to iTunes Connect. It allows you to input credentials
Try using application loader. I had the same issue with Xcode and using the loader worked for me.
I had this same issue and it resolved by making sure it logged in with the correct account.
When the modal dialog asks to select a "Development Team to use for provisioning"
Choose "View Accounts..." make sure the correct account shows in the "Apple IDs" list.
If the Apple ID is not there, use the plus sign to add a new Apple ID account.
Close the Accounts screen.
On the "Development Team to use for provisioning" use the drop down to select the account you just added, select Choose and then Validate and it will work.
I had this problem too and as some commenters point out, the reason was the different Apple ID used on itunesconnect vs. xCode.
I was able to solve it on xCode adding my itunesconnect Apple ID on xCode preferences and making sure it is selected during validation. The right team was not enough for me, it has to be the right team on right account.
I'd recommend ensuring that the account in question has been invited as both the apple developer and iTunesConnect account. This should resolve the problem. You may have to go into Preference in Xcode and re-add the account.
That happened to me with many projects , so just try to re choose your provisioning profile and code signing identity in the build settings for your project
Try using Xcode6. Xcode6.1 GM seed's iOS SDK version is now beta 8.1. You can't submit a beta binary to iTunes Store.
Related
For some reason we needed to change the package-id of our existing android application. We already use Fabric for Crashlytics.
I'm trying to bring that new app up in the Fabric dashboard, but it's not showing there, despite the device log showing no issues (as fas as I can see): device log
Any ideas why the new package-id isn't visible in our dashboard?
Best,
Sven
I experienced a very similar issue to this when building an app with multiple flavours. The solution is to manually specify the package name, and not let Fabric try to automatically grab it, as it tries very hard to "stick" your old package name.
There is a full post available (disclaimer: my site), but essentially you need to use:
Fabric.with(
Fabric.Builder(this)
.kits(Crashlytics())
.appIdentifier(BuildConfig.APPLICATION_ID)
.build()
)
Make sure to include all dependencies on their dedicated gradle.build and meta in manifest file. Next is to throw a force runtime error on your device with internet connection also do not forget to initialize it first with Fabric.with(this,new Crashlytics()). If this doesn't work try to download and install Fabric for Android plugin in Android Studio, restart the IDE and you will see a fabric icon above. Start it and select your package name.
I had the exact same problem, in the log I clearly see that the Crashlytics is in use.
I/CrashlyticsCore: Crashlytics report upload complete: <ID>
But I cannot see my project on the dashboard, and always redirect to the tutorial.
After a Build-Clean and an Android studio restart, build and run the app again to my phone, and voilá, it finds itself. Now working, without any change.
I have the same problem. After hours of researches I resolve this for my application.
First: After adding new flavour, I make changes in Firebase console (added new app in existing project, with production SHA1, changed google-services.json).
After that app does not show in fabric dashboard and fabric plugin in Android Studio. Problem was resolved after linking new app in crashlitycs in firebase console. And after that check your roles, must have Owner role (on Firebase Console Project).
I have been developing Mac App Store and iOS apps for several years now. I don't event want to know how many hours, days or weeks (?) I spend by solving provisioning problems...
One of my Mac apps targets OS X 10.7+. While everything works fine in genereal, after the last update some users reported problems when using the app on 10.7. Other OS X version work fine.
In the past, I simply cloned the project from my developing computer (iMac) to my MacBook running the specific OS X version. I then opened the project in Xcode, ran it and check what the problem was. This is far to easy for Apple, since this not possible any more.
The project only compiles (due to several reasons) in Xcode 7+ only. Xcode 7 runs on 10.10+, thus testing on 10.7 is not possible.
I have been trying to build/export the app to test it on my MacBook the whole day without any success. The app simply does not start on 10.7 on my MacBook. Of course the MacBook is a registered devices, included in my provisioning profiles, etc.
This is my workflow:
Removed all App Store specific entitlements from the app in Xcode/Target/Capabilities
Created new wildcard certificates and provisioning profiles that does not include any App Store specific entitlements
Selected the new profiles in Xcode/Target/Build Settings/Code Signing
Run Product/Archive
In Organizer select the Archive and click on Export
Here I tried several different combination (signing, no signing, etc.). No matter if I choose Export a Developer-Signed Application or Export as a Mac Application the result is always the same.
When I copy the created App file to my MacBook und start it nothing happens. The icon flashes once and this is all. Only the Console gives I hint about the Problem:
killed com.mycompany.myapp because its use of the com.apple.developer.team-identifier entitlement is not allowed.
Great... As explained I removed all entitlement from the app and from the profiles. Where the hack does this entitlement come from and how do I get rid of it?
Is there no way to test the App with all its features (== all entitlement) on another device?
I should have answered my own question earlier. Back in January I was somehow able to get the app running on my other Mac. Now I had to solve the same problem and it took some time to dig out the correct solution again.
So, maybe this will help others to solve the same problem. At least it will help my future-me to remember what has to be done :-)
Archive the app just as you would prepare the app to be submitted to the App Store.
Switch to the Organizer and select the just created archive
Select Export... instead of Upload to App Store...
Select Export a Developer ID-signed Application(second option). DO NOT select Export a Development-signed Application (third option). Actually I have no idea what's the difference is, but only the first one works...)
Click Next and the Organzier will fetch provisioning information from your dev account. DO NOT select the fetched provisioning profile but select Use local signing assets from the dropdown box instead
Click Choose and Export in the next step.
Done
Good luck and happy app signing...
To publish an IPA
I go to publish -> Distribute ad hoc/enterprise -> and then I publish the app
However, I can only publish an IPA with a distribution profile, this means I don't get any debugging on my phone.
How can I publish distributed profiles on test flight?
Solved it.
For ANYONE having this problem (i.e. being able to use a development certificate instead of production), follow the following steps.
---- Downgrade your ITunes VERSION to 11.1.5, otherwise it will complain when you try to do an iTunes sync that iTunes doesn't have enough memory!! (Titanium need to fix this!)
1) Download 11.1.5 from here http://mac.filehorse.com/download-itunes/4050/
2) Go to Applications, and Delete itunes... If you get an error message saying something like "This app is require by OSX" just go to Get Info > Sharing & Permissions > Everyone ... it has to say Read & Write.
3) Install the itunes you just downloaded
4) Open it (You might need to hold you "alt" key while opening so you can create a new library (11.2 changed something in your library that is not compatible with 11.1.5)
Then publish app USING ITUNES SYNC. (this is the ONLY way to get the development .IPA)
The app will now be in your app folder within iTunes.
You will now be able to upload your app onto test flight - a development version using a development APNS certificate. Also because it is in development mode, means that you will be able to see all error problems either through Xcode or Iphone configuration. If you publish an ad-hoc system based on production, it will not print out any Ti.App.Info etc commands in the device console.
Hope this helps! :)
Please, help me.
I would like to put an App in the IOS App Store but always receive this error message (Xcode4.3)
"No identities are available for signing"
Connect to IOS Center, Xcode can obtain identities from the IOS Dev Center...
What do I make wrong??
When you have your project open in Xcode there's a section called Code Signing. Click the first drop-down menu and you should see a list of identities, you should see at least one iPhone Developer and iPhone Distribution identity. If you don't an iPhone Distribution identity, or it is under the "identities without Provisioning profiles" subheading, you can resolve this in iOS Dev Center.
Go to iOS Dev Center > iOS Provisioning Portal > Provisioning > Distribution. You could have an expired profile, if so just modify and re-save it. If there is no profile then click New Profile. Then you should see the new iPhone Distribution identity in Xcode which you can now choose.
For me, it was the bundle identifiers that conflicted. Make sure the bundle identifier specified in Xcode > Targets > Info > Bundle Identifier matches the one you registers as App Id in IOS Dev Center > Provisioning Portal > App Ids. Hint can be found in Xcode > Targets > Build Settings > Code Signing, you just need to make the bundle identifiers match.
I was running into a problem where everything appeared to be fine (none of the certificates were expired), but Xcode was giving me that error message. However, once I downloaded and installed the .mobileprovision file it worked correctly. For some reason the Xcode automatic download wasn't working correctly.
i got the same error, when the scheme for archiving was set to "release" instead to "distribution".
Click "Manage Schemes" in XCode then "Edit..." to verify your settings.
I just renewed my iOS Developer membership. And this problem drove me crazy as I wanted to submit my app.
to Developer portal
iOS provisioning profiles
Select (your) Distribution Profile
Edit --> select the correct App ID
Generate and download it
I've created a Ad Hoc distribution profile with a couple of devices. If I want to add a couple of devices to the profile, I have to create a new profile and a build in XCODE for my app with the assigned profile.
Is there a way to make this easier? A way to make the management of the devices more simple? Without rebuilding and redistributing the app.
I hope someone can help.
You can't change the list of devices an ad-hoc app will work on without at least re-signing with xcode and redistributing the app. Sorry! I suppose Apple feel it opens up non-appstore distribution methods if you can add devices to an app already out there.
In fact you can!!
You don't have to recompile your project again. You don't even have to open XCode.
All you have to do is create a new mobileprovision file and distribute it with the existing app.
Your end users have to download and install the new mobileprovision file and app, by this order.
Here is a step-by-step.
Hugo Maurício