AppCode no product for target - ios

I am trying to run Swift iOS app in iPad simulator in AppCode. App is successfully built, but there is an error
Error running ios-app: No product for target 'ios-app'
I am quite green in iOS development and I am trying to switch from XCode to AppCode since I am more familiar with it.
I am using latest AppCode (3.1.7), everything works great in XCode.
Thanks for responses :)

I ran into the same problem - I wasn't able to run my XCTest unit tests in AppCode any more although they were running perfectly in XCode.
My error message was "No product for target ..."
I was able to get them running again by switching to the latest AppCode 3.2 build (Tascalate).
You can get this one by opening the IDE Preferences, then go to Appearence & Behavior > System Settings > Updates
There you can switch to the Early Access Program to check for updates.
Hope this solves your issue, too.
Edit: Since Julian above asked an important question about the XCode version... in my case I was using AppCode 3.1.7 and XCode 7 beta 4. The switch to AppCode 3.2 EAP - as already mentioned above - solved the issue.

I have delete the .idea folder and restart Appcode, it's work

Related

Rider Xamarin iOS error "application bundle was not generated after deployment"

I'm trying to switch from VS for Mac to Rider. My Xamarin.Forms project compiles and deploys on VS for Mac on both iOS and Android. Now I've opened the project in rider and it works great for the Android app, but when I try to run the iOS app, I get this error (after a successful build):
Application bundle was not generated after deployment
I've tried clean & rebuild, but to no avail.
Any ideas?
This happened to me today on Mac OS with the release of XCode 12.0, So what fixed it for me was to TOTALLY uninstall XCode and re down the last version I had installed, V11.6 from apple developers site https://developer.apple.com/download/more/?&name=Xcode. After that Rider will now run the iOS simulator as normal.
I guess the lesson learned is to not just update XCode until a few weeks, because I think Jetbrains need to catch up and release a newer version that works with the newer version of XCode. Of course if you need to test your app with the latest new version of iOS, then I guess you can still use VS for Mac as that still worked fine for me, but I need Rider to code, VS just doesn't do it for me at the moment
Update:
I upgraded to XCode 12 today (3/10/2020) and all seems to be working fine..
Another possible work around if it doesn't work maybe: youtrack Jetbrains
Sorry, this is a known issue with the latest release (2018.1). Already fixed and waiting to be made public as part of 2018.1.1 later this month. The only current workaround that I know is to revert to 2017.3.
Tested today.
Download the last released version directly from their website.
Now is launching iOS devices.
Rider 2.2.4
This now works for me in the 2018.2 EAP build.
Make sure you select iPhoneSimulator for your platform type under your configurations.
If you don't, you may also get the Application bundle was not generated after deployment message.
source

Xcode 8 no longer builds to device

I'm currently running Xcode 8.1 beta and have a stable release of Xcode 8 installed as well.Out of nowhere, without modifying any code inside the project, I am unable to build my project and run on a device.iOS version is 10.1 beta but the issue was not present when originally working with this version. Xcode 8 and 8.1 are experiencing the same issue and I previously did not have a problem running the project on a physical device.The provisioning profiles were up to date and I created new ones throughout the troubleshooting process.I have also gone through the basic troubleshooting options (restart the machine, restart the device, cleaned project, tried different lightning cable/USB port, reinstalled Xcode, and deleted Xcode preference files).The project builds and runs very quickly to the simulator and when attempting to run on the device I received no errors.When trying to run on a device, the build goes through the first tenth of the process and just sits there until I cancel it. I've even created new test projects to test against a known good and the issue persists.If anyone has experienced, a similar issue your insight would be greatly appreciated.
I was facing the same issue but installed latest Xcode 8.1 and issue got resolved
When you have multiple versions of Xcode installed the command line tools loses track of which Xcode to run. Make sure that this is set. Having multiple versions has always been troublesome for me.
The issue ended up being with a large number of dictionaries. The compiler was attempting to go through a rather large number of dictionaries and was unable to complete. I restructured my data model and the issue was resolved.

Appcelerator application throwing app.js not found on device

Recently I have upgraded all my iOS and Appcelerator kits to latest versions, and since then I have problems while preparing archive / builds.
Initially the app was throwing error on simulator but I found a way to resolve this.
Plz note I am using Xcode instead of Appcelerator for building archives
The steps I took to run the app successfully in simulator...
1. Xcode->Preferences->locations
2. Derived Data -> Advanced -> Custom: Relative to Workspace
3. Now build in Xcode it should not have that problem.
Now build is working fine in simulator, but I can still see app.js not found error on the device (I build the archive and installed via iTunes)
Thanks in advance... People having experience in using Xcode 7 may reply to this in a better way.
This is an known issue:
https://jira.appcelerator.org/browse/TIMOB-19818
Please use Appcelerator's JIRA to report and track bugs.
And as people have commented, you should not actually need to build form Xcode as the CLI and Studio will do this for you via the Xcode command line.
My issue was because we were using camelCase as the project name "I think!!!"

Xcode 7 ValidateEmbeddedBinary error Could not read data in foo-WatchKit-App.app

I am trying to do a full build on an iOS App with a WatchKit App as well.
When compiling the full project for Archive I am seeing the following
ValidateEmbeddedBinary DerivedData/lifa93/Build/Intermediates/ArchiveIntermediates/lifa93Dev/BuildProductsPath/Release-iphoneos/lifa93.app/Watch/lifa93-WatchKit-App.app
cd /Users/lordandrei/Projects/git/X7/lifa93
export PATH="/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
builtin-embeddedBinaryValidationUtility /Users/lordandrei/Projects/git/X7/lifa93/DerivedData/lifa93/Build/Intermediates/ArchiveIntermediates/lifa93Dev/BuildProductsPath/Release-iphoneos/lifa93.app/Watch/lifa93-WatchKit-App.app -signing-cert *9F…FB* -info-plist-path /Users/lordandrei/Projects/git/X7/lifa93/DerivedData/lifa93/Build/Intermediates/ArchiveIntermediates/lifa93Dev/InstallationBuildProductsLocation/Applications/lifa93.app/Info.plist
error: warning: Could not read data in /Users/lordandrei/Projects/git/X7/lifa93/DerivedData/lifa93/Build/Intermediates/ArchiveIntermediates/lifa93Dev/BuildProductsPath/Release-iphoneos/lifa93.app/Watch/lifa93-WatchKit-App.app
I have tried:
toggling between Debug and Release
toggling No Install and No Validate.
revoking and replacing all profiles (Signing, adhoc, dist)
So far nothing has made a dent.
Suggestions welcome as I am in a holding pattern trying to build.
Xcode: Version 7.0 beta 3 (7A152u)
iOS: 9.0 beta 3 (13A4293g)
Radar: 21975256
I had this issue when I was trying to build to my iPhone 6+ and Watch. I had just re-installed Xcode 7 Beta because I accidentally deleted one of the needed frameworks. I tried building several times and received the same "Could not read data..." error. I finally built to the simulator successfully, AND THEN built to both devices and it worked.
My issue now is that builds to Apple Watch seem to take forever to run or pass "Attaching...".
I don't know exact reason of your problem, but I created new project that includes WatchKit App target as well. And it works fine, no problems with building process.
I am using Xcode 7 beta (7A120f).
That's why I propose 3 potential ways to resolve the issue:
1. Create new new project from scratch and migrate source and resource files from your current project to new one. I had similar problems (it wasn't related to WatchKit app) previously and this trick helped me.
2. Install latest version of Xcode. Xcode 7 beta 4 is released on 21st of July.
3. Install Xcode (7A120f). This is version that I am using, you are using different one. I don't think that it will help, but who knows.

XcodeColors with Xcode 5.1 + crashes with iOS dev

[Running OS X 10.8]
It worked fine with Xcode 5.
Now got the latest XcodeColors from GitHub (5b8da92 : Xcode 5.1 support), built it under my Xcode 5.1 environment and the TestXcodeColors app fails to write out in colour.
Worse yet, moving on to debugging my app under the iOS simulator crashes Xcode due to having the XcodeColors plug-in. Removing it makes things work, but of course without colours in my console view. (boo)
XcodeColors destabilizes Xcode 5.1.
Anyone else experience this or found a way to get it functioning?
It looks like there are two possible causes for this crash: 1) OSX 10.8 2) Choosing to convert the program to ARC
A solution seems to have been found:
1) Delete your existing install of the plugin (~/Library/Application Support/developer/Shared/Xcode/plugin-ins/XcodeColors.xcplugin)
2) Download a fresh copy
3) Open it and do not choose to convert to ARC
If you are on 10.8:
4) Open the build settings
5) Change the Base SDK to 10.8
That's it. Otherwise, follow standard instructions (build it, restart Xcode, verify with the test program)
I had the same issue here. I just installed Xcode 5.1 with all my newly built plugins. This one crashed and I did some analysis and couldn't understand why it crashed! It all looked fine to me. I did convert the code to ARC but it didn't seem to be important for this issue.
Last resort: reboot machine. And voilà it worked! Go figure…
Ran the test and the Console output is now nicely coloured. Hope this helps you although it doesn't answer the question.

Resources