I've been able to create and upload one new iOS app and two new Android apps in Fabric however, this particular iOS build will not upload to Fabric. I have gone through all the motions outlined in their tutorials and can run fastlane beta which runs successfully and says
[15:14:12]: Uploading the build to Crashlytics Beta. Time for some ☕️.
[15:14:20]: Build successfully uploaded to Crashlytics Beta 🌷
[15:14:20]: Visit https://fabric.io/_/beta to add release notes and notify testers.
However, this doesn't produce an app in Fabric. When I run through the steps for a Crashlytics upload either using the manual option or using the Mac App, I am unsuccessful. The Fabric app just leaves me with "to continue, build your Xcode project by pressing command-B," which does not do anything, I'm just stuck at that screen. I have tried every answer outlined in the Stack Overflow post here which should have addressed this problem but does not for me.
In short, I have successfully uploaded two Android apps and an iOS app to Fabric using this workflow but cannot get this iOS app to upload regardless of what's indicated by the command line.
If it matters, this is Cordova app.
The answer was tricky and bizarre so I'll post it for future reference. The trick was two steps (as far as I can tell, this is what made it work). First, run:
./Crashlytics.framework/submit *api_key* *build_secret* -ipaPath ./buildname.ipa -emails ***#*** -notifications YES
in the directory which contains your Crashlytics.framework file. This is probably the same folder as your xcodeproj file for your app. You should have this file in that directory after following the steps outlined in my post above.
Then open the xcodeproj and build and run the file (for me I had to run it on an emulator not just the physical iPhone I had connected to my Mac).
This created a new Fabric app. I have not seen any answers like this on Stack Overflow so hopefully this is helps anyone like me. I still have no idea what the root issue really was here.
I'm just trying out iOS development and no way willing to pay $99 to try out something. I have a running project that works on android and I wanted to see how it looks on iPhone but it seems I'm stuck on all sides.
First of all, I've installed Sidekick and setup Nativescript on the mac and tns doctor reports no issues (I originally made the project on Windows with Android phone). Now I'm trying to do a local build but I get an error:
[18-10-19 22:49:00.401] Error detected during LiveSync on 9991865793b34ae30366571031b6c251590c222a for /Users/vipulk/Documents/YO. Error: ENOENT: no such file or directory, scandir '/Users/vipulk/Library/MobileDevice/Provisioning Profiles/'
I think this is related to certificates and provisioning profiles. I thought you didn't needed those for local builds. Anyways, The sidekick's Auto Generate is of no use either as it doesn't work with 2FA accounts.
I tried to use this guide to create these files manually. I created the csr file but step 6 asks you to go to this page which asks you to use your development program. Again, don't have that.
The cloud build also needs certificates.
What do I do?
The NativeScript Book has two chapters at the end on iOS deployment, and they address your question, though they don't use sidekick. But, hey, nothing wrong with the good old {N} CLI.
yesterday I wanted to deploy some bugfixes for my app with Xcode 8.3, and ran while uploading into the error ITMS-90167: "No .app bundles found in the package".
This error is also shown already when trying to validate.
I did not change any code signing or mobile prov. files. Everything worked a month before.
I tested my code with ios 11 device support copied over from xcode-beta.
I read through all stackoverflow questions like this one, but I am not using Xcode 7 nor the application loader.
So I updated to Xcode 9.0, fixed some stuff due to the changes for swift 3.2, cleaned derived data etc., and tried again but still the same error.
Inside the ipa I can see the folder Payload/appname.app with its contents.
I am trying to deploy with fastlane, but also tried with Xcode, same results.
I have double checked code signing and recreated mobile provisioning profiles, revoked expired certificates and deleted duplicate/expired certs and keys in my keychain.
Xcode shows the profiles as eligible.
I also tried Automatically manage signing.
But nothing helped.
What does this strange error message really mean? And how can one debug/resolve this?
For me, the cause was a lack of space on my internal hard drive.
As far as I can gather, you need to have the same amount of space free that the unarchived xCode project takes up in order for the .ipa to be verified and uploaded to iTunes Connect - and that's through either xCode or ApplicationLoader.
After moving as much as possible over to a USB drive, the .ipa uploaded without issue.
I finally resolved the issue (after 2 days hard work),
it seems that it was a problem with a framework which I copied (with all sources) completely into my app-project and within this framework there was a info.plist (of that framework) which seems to confuse the validation step of the itsm transporter. Although the app was built and worked in simulator and on the device correctly.
The error message
ITMS-90167: "No .app bundles found in the package"
is very misleading - because there was an .app directory in the ipa and I first thought about signing issues. On the internet I didn’t find anything helpful with this error.
After I build the framework as separate project and included it correctly as a framework the validation was successful and I was able to upload my app.
If anyone knows more about this itms transporter and where to find some more documentation about possible errors, please leave a comment...
I've had an iOS project in fairly stable condition up until Xcode 8's public release. After a bit of confusion with the Migrator, I finally convinced the compiler that I did not want to go Swift 3 yet, and that my code was indeed valid Swift 2.3. Not sure if this at all relates to what the Organizer does in validating my long-awaited archive with some long-overdue fixes for iOS 10, but we'll see...
Anyway, I got Xcode to archive my latest build (which runs fine on my iPhone 5s by the way). I tell Organizer to "Validate..." in preparation for an upload to iTunes Connect. After a good deal of doing its thing, it finally spits this at me:
Been at this for three days now. Application Loader gives me something similar, but not much more helpful:
Following the suggestions in this answer, I find that every single one of my compiled assets read as sRGB, not 16-bit, or P3. Aside: When does an API analysis file get "too large"? I mean, sure I use Apple's APIs a lot, but I can't be alone in that. That's what they're for, right?
I've tried (almost) everything I can think of. I've redone my code signing a dozen different ways, read and recombobulated the build settings wherever I thought could be relevant, and tried every combination of bitcode and symbol inclusion available to me. Just about everything I could come up with short of migrating to Swift 3! Could that really be my solution? It's a rather big jump, and with the time I have, I'd prefer to get this working build out to my users before I'm slammed too hard to shore up the updated codebase.
I can't seem to find anything on "ITunesSoftwareServiceAuthenticationErrorDomain", or this mysterious "error 434". The only reference I've found so far leads to a dead StackOverflow question. Really wish the author hadn't removed it... Wonder if he found his answer?
So my question is as follows: What am I doing wrong to get these errors, and how can I fix them? I'd rather not have to upload without symbols or bitcode, so if that's the workaround, I'd like to know why, so I'm not limiting myself for something dumb.
Cheers!
I had the same problem with Xcode 8.2 while submitting my application:
ITunesSoftwareServiceAuthenticationErrorDomain error 434.
Solution: I switched to different network and it worked for me.
Bump the build number and validate again.
Had the exact same problem. I tried upgrading to Sierra which seemed to update bits of Xcode etc. The new error message was formatted differently, so I could not see the "434"
(With 1 success in 15 attempts (I had to tweak a version number in a string in the app, so didn't choose to upload after that brief moment of joy), i just uploaded the archive anyway, and after 2 hours of processing, it was accepted. I will update when my new app version is live to verify this error can be safely ignored, at least in some cases (e.g. I checked all my graphics' color profiles, etc.).
Do the below steps :-
1. Analyze the project. (From Product Menu)
2. Click on Archive. (From Product Menu)
3. Select the development team for provisioning.
4. From summary window unselect "Include bitcode" and click on Validate button.
Now, It will working fine.
I solved it by uploading my app through Application Loader.
Archive app Export ipa iOS Deployment
Xcode-> open developer tool -> Application loader
I had the same problem while I was trying to submit the app to client's iTunesConnect account. I've signed in with new apple id, downloaded the certificates and provisionin profiles but still got this error:
(ITunesSoftwareServiceAuthenticationErrorDomain error 434.)
How to fix this error?
Try to remove Provisioning Profiles files at ~/Library/MobileDevice/Provisioning Profiles/
Make new Build and Archive the app. Xcode will create new Provisioning Profiles and submit the app to iTunesConnect.
Just to share this.
Quit xcode and re-login as suggested by members does not work for me. I solved it by using "Application Loader"
Steps: 1) change the version and build in your App 2) archive again for new file submission and export file to desktop 3) goto top menu: Open Developer Tool > Application Loader (if you don't have this , search, download and install this plug init) 4) upload the new version archived file. Done
You will find them in iTune Connect. From here process to My Apps > choose the rejected app > change the version and click on the new uploaded archive file, file will be processing..
5) time to resubmit :) cheers
Clicked Valid until it succeeded, 3rd time.
Since there seem to be many solutions to this problem, it may just be an issue not related to anything developers have control over and the "solutions" seem to be "solutions" because after some action was taken, it succeeded. The action I took was the non-action... and it was successful.
Hope this helps, as this is a stressful problem to have when you cannot upload your app and muddling around in Xcode to fix it you might break something else.
I fixed it by upload using Application Loader.
Besides, after upload the app i receive the warning about Privacy - Photo Library Usage Description and Privacy - Camera Usage Description, so that, please make sure you have them in your info
Hope it help!
I had the same problem. In my case it was caused by following. I had a lot of png-files in assets.xcassets and some of them had AdobeRGB Color profile. I changed the profiles to sRGB and xcode validated the archive with no error.
Frankly speaking, when I changed the profiles some other strange errors occured, but they dissapeared by themselves when I tried to re-validate the acrchive several hours later (I did nothing just waited).
If this occurred randomly, try to delete that archive and make sure you have "Generic iOS Device" selected as target when you run Product > Archive again. This solved it for me.
I Got the same issues when i try first time.Next time it Validated successfully. Please check network once before trying second time.
1.Cmd+Shift+K
2.Close Xcode
3.Open Xcode
4.Cmd+B
5.Product->Archive
Just Clear all file in Path ~/Library/MobileDevice/Provisioning Profiles
Go to Xcode Select Provisioning profile again and then it auto-generate again.
So It will be working fine.
In my case it was the following:
my account had been logged out and I had to enter the password again
Xcode v8.0 had to be updated to 9.x to be able to publish to the App Store (as of July 2018)
I fixed this problem by updating Xcode from 8.2 to 9.
Apparently there was a compatibility issue with an SDK used internally. Xcode was not helping with it's error message. I discovered it by using the Application Loader to upload the archive. Application Loader's error message made some sense.
So I'm trying to share my project (iOS/Swift) with team members and I hosted it on Bitbucket. They have no issue downloading the latest repo and launching it, but the build is getting errors because of dependency issues with a few external frameworks. Originally this was occurring because I didn't actually upload those frameworks to Bitbucket, but since then I've moved them into the project director and re-linked them to the project, but still getting errors:
I've included those frameworks into the project just as described in their READMEs (e.g. https://github.com/Alamofire/Alamofire) and everything works great on my computer, so I'm not really sure how to go about fixing this issue.
According to the error message, it is Code Sign issues rather than external framework issues.
Please be sure your team sharing same p12 file and provision