When I build my app on my iPhone in Xcode there's no problem at all but when I get IPA output(ad-hoc) it seems one of my buttons which I used an third-party library (ANLongTapButton) for that doesn't work well and it crashes.
While I was getting IPA output I made sure that library is added.
what's wrong?!!
Related
We've been developing and testing a Watchkit Extension app (iOS 12.1 and WatchOS 5.1) for the past few months and successfully testing it on a simulator and local, connected devices (iPhoneX + Watch 4) using xCode 10.1.
This past week we built an archive for posting to App Store Connect. We got stuck in the Archive Organizer after archiving for release. The "Validate Content" button was disabled, the Version is blank, the Identifier is blank, and the Type is "Generic Xcode Archive". Unfortunately, all we can do is export the .app files from the Archive Organizer; we can't push the archive to App Store Connect.
We made sure the build scheme was set to Release and we archived to a Generic iOS and WatchOS device. We also set Skip Install for the three targets (iOS app, Watch app, Watch extension) to No as we assumed none of those are static libraries. We even tried every permutation of Skip Install settings. We looked at the issue in the following link and we have no Header steps in the Build Phases of any targets:
https://developer.apple.com/library/archive/technotes/tn2215/_index.html#//apple_ref/doc/uid/DTS40011221-CH1-PROJ
We have two frameworks we included in the project using carthage. We thought maybe these were causing issues, but we rolled back to a branch before we added them and still have the same problem.
We made sure the build in the Scheme is set to a single target and cleared out the Derived Data folder. Still no dice.
I’m not 100% sure from your question, but are you trying to push an archive of the watch app to the App Store?
If so, that’s not how you submit the app. The Watch app is embedded in the “regular” iOS app, and to distribute it you need to archive and submit that app as usual.
If I’ve misunderstood, feel free to ignore this!
I had the exact same problem. When I changed Skip install on the watch app and watch app extension to YES, it suddenly worked. No idea why.
Not too sure if this is programming-related enough.
I'm using Xcode 9.2.
My organization is looking to deploy a custom iOS app built using our Apple Enterprise account. We are using Blackberry UEM to deploy the app. The problem we're seeing right now is that the high-res app store icon in Assets.xcassets gets stripped out when archiving my IPA, so when we add it to UEM, the icon looks quite bad in the UEM store page. I've tried playing around with the archive settings, including app thinning, compiling from bitcode and stripping swift symbols.
How can I force Xcode to leave the store icon in my xcassets in the final built ipa file?
Recently updated to Xcode 6 and now whenever I archive a project, I get a .pkg instead of an .ipa. I've set the other target in my project (cocoapods) to skip install but that didn't do the trick. The deployment target is iOS, not mac (it's an iphone/ipad app that previously archived .ipas fine).
Am I missing a new setting somewhere (i.e. default archive iOS apps to .ipa) or is there a gotcha with ad hoc distribution on Xcode 6 I'm not aware of?
Add LSRequiresIPhoneOS YES to your Info.plist
The key can be found as Application requires iPhone environment
I couldn't find a direct way to do this in the Xcode 6 GM (or betas), but found a couple solutions that have worked:
Archive in Xcode 6 and export in Xcode 5. This worked for me while I was using the betas, but after installing the GM, the Xcode.app binary overwrote my Xcode 5 version (This could be easily reinstalled). #Anan answered that here.
Grab the .app file from your .xarchive and package your own .ipa by creating a Payload directory, copying the .app into it, zipping it, and renaming the extension to .ipa.
I tried using the TestFlight desktop app and dragged the archive into it after creating an account. This seemed to go through the motions of packaging the .ipa and uploading it to the TestFlight servers. I wasn't able to find a trace of the .ipa on my local machine. This probably works, just not sure where to grab the .ipa. You would have to generate the .plist on your own or use an old one.
Regardless, this seems like a bug and these workarounds are annoying to have to do for something that used to take 5 seconds to complete.
Steve
I recently upgraded my PhoneGap app from 2.4.0 to 3.4.0. To do this I had to create a new project using NodeJS, then copy all the www files and resources into the new project. I added a new ios platform. It compiles and runs in xcode 5.1. The simulator works too.
Now I want to submit this to the app store as an update to my previous version. The problem is the "Product > Archive" menu in xcode is disabled.
Has anybody who can give me some direction been through this process? Or direct me to where I can get some help?
======
UPDATE: I found that I the target device must be set to iOS Device in order to archive a project. Now Archive is enabled. I run archive, but no archive is listed in the Organizer.
Still looking for help.
Make sure you connect your device first. You cannot archive your project without a device.
This turns out to be a simple oddity with Xcode. If you have a simulator selected you cannot archive. Choose iOS Device and then you can archive, with or without an actual physical device connected.
I have a project that looks awesome on the Simulator and on iOS device if I build and Run with Xcode, but if I achieve the project and upload to TestFlighApp, when I download the app on the same iPad I tested the project previously, it looks different.
Does anybody knows why this happens? I have no clue on how to debug this.
Please refer to the following sample, both screenshots taken from the device, one using the IPA and other running from Xcode on iOS device.
Those black lines.. I don't know where they come from
The problem can be in Compress PNG Files option in your project Build settings.
Also check that build configurations of XCode scheme for Run and Archive are the same (must be Release).