Where do these five images come from?
They seem to be installed on all iOS simulators when launched via Xcode 6. Even after resetting the simulator they show up.
I ask because I want to depend on these images being there for automated testing but can't track down where they are coming from.
They come from the sample content that is installed when simulators are created or erased. This content is located in the simruntime bundle.
See /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS 8.1.simruntime/Contents/Resources/SampleContent
Related
I am trying to use Zombies with my Xcode iOS project. When I click on the red button, I select the simulator I'm using, but then it takes me into what looks like is my mac folders directory. I wonder if I'm supposed to find the "Simulator" app, if there is such a thing. I found in the Library/Developer/CoreSimulator/Runtimes/ three items that say "iOS ..simruntime, but there is not one that represents the iOS version my Simulator is running.
I'm not sure I'm even on the right track. I think I was able to get right as far as clicking the red button while my project is running in simulator. What should I do once I do that and the window appears to select an "app"?
I cleaned out my personal library in attempt to fix a Xcode behavior bug.
But now I can't see the available SDKs/schema.
I believe the SDKs are with the Xcode bundle, having just download a fresh Xcode from the App Store.
So now I only see 'device'.
How to I force Xcode to reveal the simulators?
BTW: I can see all the simulators from the SAME Xcode app via my Guest account.
So my own Xcode environment is screwed up. Is there a remedy?
Comparing the Guest to my own account, I noticed that I didn't have any simulated device.
So I did the following:
1) I copied all the installed simulated devices from my Guest account to my account.
$~/Library/Developer/CoreSimulator/Devices
2) I noticed that this wasn't enough. Xcode still could not 'see' these devices. So I rebooted in Disk Utility and did a general repair of the entire drive.
Disk Utility noticed some unmapped regions (no doubt my 'erroneous' drives) and the repair fixed it.
Now I got my simulators back.
I have a webapp that I created well over a year ago, and running on iOS 6, it's been rock solid. It's designed to work offline and online, from the same home screen icon. I've got a manifest file that loads up the bootstrap javascript, all the js includes, and the core files. The app is designed to store data while offline (using SQLite) then transfer anything in the offline queue to a MySQL database once online. And again, all this was working on iOS 6 with absolutely no changes whatsoever to any of the files, the manifest, etc. for months.
Then I upgraded to iOS 7.
Now I have a host of problems, but they all seem to revolve around database issues. I'm getting a lot of code 6 errors in Chrome (in Safari, I get nothing, just a blank screen). In my reading up on this I found that Apple did make some sort of change to how SQLite runs, but not being an xcode developer I don't have access to the materials on Apple's site, and since I'm not running xcode in any case I don't know if that even applies to my purely HTML app.
My question, then, is this: with whatever changes Apple made on the app side, is there anything that would have affected the functionality of a pure HTML5/JS/SQLite offline web app, bookmarked to the home page via Safari?
IOS 7 limit browser DB size from 50MB to 5MB , is that the reason ? Also I met a end user turn on Private Browsing in their IPAD , also could cause this trouble, hope that helps.
you can check this :http://www.mobilexweb.com/blog/safari-ios7-html5-problems-apis-review
I figgured it out.When you enter safari, a little button on the top left on the keyboard says "private", click it to disable it. The database will work fine. But! jquery mobile will not be able to use the back button. For this, you have to delete appcache from your code. jquerymobile 1.4 will fix this, but for now you will have to live without appcache!
I only use the iOS simulator for testing websites, not actual apps. Today I opened it up and it keeps asking me for an app for it to simulate. If I click cancel, it just quits the simulator.
I've tried deleting preference files, but I'm just not familiar enough with the simulator to know what's going on. How can I just get this back to normal, or satisfy this dialog?
I think you could try the menu
iOS Simulator -> Reset Content and Settings...
This would clean your simulator storage.
Update
According to this link, Cleaning up the iPhone simulator
move to path
/Users/<username>/Library/Application Support/iPhone Simulator/{6.0 / 6.1}
You could try to clean it manually
I have this jailbroken iPhone 3G with iOS version 4.2.1 (the latest supported version). When I connect it to Xcode 4.2, Xcode starts copying the debug symbols. It stops copying towards the end of the process, and shows the following error:
Xcode has encountered an unexpected error (0xC002)
No such file or directory, at ‘/SourceCache/DTDeviceKit/DTDeviceKit-867/DTDeviceKit/DTDeviceKit_Utilities.m:864’
Anybody experiencing anything similar?
I know I should try and restore the phone, but I'm asking just in case anybody can come up with a solution that doesn't involve restoring it.
In this post on mactechnews.de, one guy reports the same problem -- with no solution, so far.
Alright, after a lot of testing and digging up the filesystem... I solved it.
It turns out that there are just a few files that are not downloaded from the device (for reasons still unknown). They are related to the dyld cache (don't really know what this is and what it's for). Here are the steps to make your 4.2.1 device debuggable in XCode 4.2 and 4.3.x:
Close Xcode
Go to: ~/Library/Developer/Xcode/iOS DeviceSupport/4.2.1 (8C148)/Symbols/System/Library/Caches/com.apple.dyld/ Note: if you don't have this folder, run Xcode, connect your device, and wait until the error 0xC002 appears in Organizer - the folder should be created by that time.
Create 3 empty files there called:
.copied_dyld_shared_cache_armv6
.processed_dyld_shared_cache_armv6
dyld_shared_cache_armv6
Run Xcode and enjoy the light next to your device eventually go green:)
Or, for the terminal lovers:
cd ~/Library/Developer/Xcode/iOS\ DeviceSupport/4.2.1\ \(8C148\)/Symbols/System/Library/Caches/com.apple.dyld/
touch .copied_dyld_shared_cache_armv6
touch .processed_dyld_shared_cache_armv6
touch dyld_shared_cache_armv6
This is obviously a hack but it works perfectly for debugging and I haven't noticed any side-effects so far.
Enjoy!
Small update:
I tested it on my snow leopard hackintosh, with the Xcode 4.2 (most recent to date) and although the device is active in the organizer and it is possible to run the app on the device, i get black screen on launch. It gets installed but apparently debugger cannot get attached. I had the same problem with 4.0.2, when the 0xC002 problem didn't yet occur so I think it's unrelated and might even not happen to others. Nevertheless, 0xC002 is still solved.
On my main development machine with Lion and Xcode 4.3.2, device is perfectly debuggable.
The answer above (https://stackoverflow.com/a/9944892/1390251) works, basically,
but for newer versions of Xcode you probably need to rename the files as follows,
having them end with '7' instead of '6':
touch .copied_dyld_shared_cache_armv7
touch .processed_dyld_shared_cache_armv7
touch dyld_shared_cache_armv7
If not sure, you can keep both sets of files (...6 and ...7)
in the relevant folder (can also be 5.1.1 for that matter)
and it should work.
(have tested it on iPhone 4 with iOS v5.1.1 genuine)
It seems that you cannot debug apps on iOS 4.2.1. I tried several restores to iOS 4.2.1 with same effect. Downgrading to iOS 4.0 was the only thing that worked.
The reason for whole problem is that iOS 4.2.1 is not supported in XCode, according to this website.
Error in Xcode getting debugging info from 5.0.1 iphone
solved, see the link to archive with iOS5.0.1 debug info
download & unpack to "~/Library/Developer/xCode/iOS DeviceSupport/" & be happy =)
I fixed this bug in![enter image description here][1] this way:
I duplicate the 5.1.1(9B206), rename it to 5.1.1(9A405)[my ios device is this version], then the error is gone.