I have created a new project in Xcode 7.3.1 and added images in device specific xcassets. When I open preview of storyboard in Assistant editor, I am not able to see the image in any screen size. If I choose universal, they start showing up. Same happens for iPad storyboard as well. Please see the attached screenshots and please help.
Above image is showing up in assistant editor because it is added in 1x and 2x of universal. The below image is not showing because of being added in device specific1
I got the same problem as you today... I think this is a bug of Xcode, below is the way to fix the issue:
Close the project you are working on with.
Delete your project's【DerivedData】folder.
This folder may inside your project's folder, or inside
~/Library/Developer/Xcode/DerivedData/(your project)/
or else run this in terminal
rm -rf ~/Library/Developer/Xcode/DerivedData
or somewhere else that was setup by you.
restart your project.
After these steps, the problem should be solved. And from my experience, these steps can solve many Xcode problems, so if you got some problem with Xcode again, try these steps first.
I guess this is related to XCode's internal workings to pick up the images. As the images (device specific) are not shown in the storyboard but they do show when you run the project either in Simulator or in device.
Related
Using Xcode 5.1 to debug an iOS 7.1 iPad application.
When I build and run my project in the iOS Simulator, the simulator opens and my app icon pops up for a second. Then it looks like the app stops installing and the simulator goes to the home screen. Xcode still thinks it's debugging and it doesn't show any errors in Xcode or the simulator. I can go to my app in the simulator and click it again, but it just crashes. I get the same behavior in iPad, iPad Retina, and iPad Retina (64 bit). Any subsequent tries to run the app in the simulator doesn't even attempt to pop the app icon up until I quit the iOS Simulator and try again. All the usual fixes haven't worked for me yet.
Fixes I've Tried:
1. iOS Simulator > Reset Content and Settings...
2. Window(in Xcode) > Organizer > Delete Derived Data & Delete Snapshots
3. Delete Contents in ~/Library/Application Support/iPhone Simulator
4. Uninstall Xcode and reinstall
5. Clean project and rebuild
6. Restart machine
I'm out of ideas. Is there something I've missed?
Thanks all!
Create another app with the exact same template and look at the app delegates and make sure they are the same.
Example: AppDelegate.h and AppDelegate.m
You might've accidentally deleted an area that helps load the App.
Alright I found the problem. I was playing with how we load our frameworks because we were having other issues before and I left a bad value in our Linking settings.
Here's how I fixed it:
Project > Build Settings > Linking > Mach-O Type set to "Executable"
It was set to "Bundles" before which causes Xcode to package the app in a way that caused ours to break.
Helpful Post: In Xcode project target build settings, What is Mach-O Type?
I'm trying to run an app made on Titanium in my cellphone. At first it was working fine, until i decided to debug my code. After that whenever i try to run it on my cellphone, it gets stuck # the powered by titanium screen (that red one).
I tried to delete my build folder as some people said after a bit o research but it won't work.
How can i solve this?
What I would try to do is:
clean the project (it also deletes the build folder, but I think it also cleans some more stuff in there).
when the app starts try to set an alert in app.js as the first thing - see if this alert shows, and if it does - move it to the next step until you find a place where it is no longer shown which might indicate that this is where you problem is.
Look at the device logs - if it's an android device open ddms and look at the logs while you run the app - see if anything pops up. If it's an iPhone on xCode you have some sort of console viewer for the phone (sorry - can't remember the name right now).
make sure you are not still running under debug mode.
BTW - you didn't mention if it happens on iPhone or Android? does it happens on the simulator as well?
I was having the same issue. From digging through Appcelerator's Jira I found we weren't alone, and also got a workaround that allows us to get past the splash screen. Check to see if there is a deploy.json file located in your application's directory on the device. If so delete it!
Here is more info on the issue https://jira.appcelerator.org/browse/TIMOB-16086.
It's rated as a high priority to be corrected for the 3.3.0 SDK release.
I don't know what has happened to my Xcode, but since I deleted my app from the device, and tried to rerun it on my iPhone, I get this message coming from the top of the screen:
No such file or directory (/Users/spazm/Library/Developer/Xcode/DerivedData/newProject-cfjhjgezzcapwoadaivpptyywptu/Build/Products/Debug-iphoneos/proj.app/proj)
In addition, where you can select the "active scheme" (iPhone / iPhone Simulator / iPad Simulator), I used to have "iOS device", and right after plugging my device in, I would get my phone's name and everything would go sweet.
Now, I only see "iOS device" (after plugging in), and I need to select my phone manually, which seems like something went wrong here. I am not sure what.
In the xcode organizer delete "derived data"
Alternatively you can open "~/Library/Developer/Xcode/DerivedData" folder and delete derived data folders associated with your application. You also should make a clean/build.
For the second problem, again in the organizer window under devices find your device and click "use for development"
Edit: Today I have experienced again, deleting derived data did not solved the error this time. After deleting data, making a clean build, deleting the app from my device, I needed to close & reopen xcode, which finally fixed the error.
The problem was in the project file itself. Used my backup to load the old project, then manually added all the files from the bad-new-project.
Must have been some setting.
Try checking the Deployment Target for the app. I was getting this same error when trying to deploy an app that required iOS 6.0 to a device that had 5.1 installed.
Recently I updated my project settings as Xcode recommended. I just pressed a button and they did "everything". However now when I try to run my app on my device it freezes on the loading bar at about 75% and then after 15 seconds it says "build succeeded" but does not run on my device and everything stops as if I had pressed the stop button. I am getting no errors but I am getting the following warnings. It works on the simulator just fine.
For the record I have looked this up and everyone says to add "armv6 or armv7" and I already have this done. I am running deployment target iOS 3.0+
If anyone can help me, it would be appreciated. Thank you!
EDIT
Works on my device when I run leaks in instruments... but won't without instruments
Well, I can't really say much specific here, but if all else fails, I'd try making a new project and copying the content of this project to the new one. This could fix some underlying problems that may have developed in the build settings etc.
I got a application from my teammate, and it is for both iphone and ipad devices (which it is developed under iPhone SDK 3.2).
I have iPhone SDK 3.1.3 installed in my mac book. When i tried to compile the application for iphone simulator i got the following error.
Interface builder is unable to open documents of type iPad XIB.
The above error is for interface builder created for ipad.
My Question is we can't compile the application on iPhone SDK 3.1.3 which the application developed under iPhone SDK 3.2?
Please shed some light of this?
thanks
mindus
Go to your project settings, and delete the line that says Interface Builder Plugin search path or something similar.
the exact line in project.pbxproj is: IBC_PLUGIN_SEARCH_PATHS = "${PROJECT_DIR}/**";
Short answer
Temporarily remove the iPad xib when working with the 3.1.3 SDK. Put them back when you go back to 3.2 and above.
Longer answer
This cropped up for me when compiling against 3.1.3. You can use conditional compiling to get code user newer features to build successfully (see Matt Gallagher's helpful post on conditional compiling).
There may be a smarter way to tell the compiler not to look at the iPad xibs. For testing on the 3.1.3 simulator I simply made a copy all my iPad xibs and then removed them from the xcode project. When going back to my current development set up, you have to put them back. It's a bit of pain, but not that fiddly.
To fix this:
Press Command-1 to go to the project tree
Select your project
The in the right panel select your project, and then click on "Build Settings"
In search field just below the "Build Settings" enter: "Overriding Plug-In"
Now, the only visible setting left should say "Overriding Plug-In and Framework Directory"
Double-click the value and remove all entries using "-" button
Click somewhere else so settings are saved
That should fix it