-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS8/Xcode 6 - sim-public link is invalid #396
Comments
#395 is likely a related issue. |
This directory moved in Xcode 6. This StackOverflow article is helpful: http://stackoverflow.com/questions/25198840/document-directory-path-of-ios-8-beta-simulator It's a bit convoluted getting to the directory. First you need the UDID for the simulator profile you are using. This is specific to a specific device/version combination. This will need update I suggested in #394. Then you need an application-specific UDID to form another part of the path. This does not seem to be the same as the application UDID though. I only identified my app by watching the filesystem when I ran the app. Not sure if a Here is an example path to the application DATA on OSX. The first UDID you see is for the iPhone 5S device for ios8. The second UDID is for the app. You'll have to poke around in the directories and understand the new layout. /Users/jon/Library/Developer/CoreSimulator/Devices/45517293-B71B-4145-B079-16ECC5FF259F/data/Containers/Data/Application/32659D47-E748-4035-8364-CE6E96B1C294 |
Useful workaround: http://simpholders.com |
This is still an Issue with release 5.0.25 |
5.0.25 was not intended to build with Xcode 6.1.1/iOS 8! This has now been fixed in 5.0-SP3 candidate as of at least commit b9eb121. (Actually, I think some commits back.) It now works nicely, and no need for SimPholders. |
lrwxr-xr-x 1 jon staff 154 Sep 22 14:55 sim-public-8.0 -> /Users/jon/Library/Application Support/iPhone Simulator/8.0/Applications/7DF5A015-DA92-4037-BF3F-FA25D2ADC19D/Library/Caches/Private Documents/apps/public
It's an invalid symlink.
The text was updated successfully, but these errors were encountered: