In recent Swift it should be even easier and NSData is no longer needed. let s = “String to encode” let encodedDataArray = [UInt8](s.utf8) outputstream.write(encodedDataArray, maxLength: encodedDataArray.count) Arrays can be accessed as buffers of the correct their type (see withUnsafeBufferPointer). I think the array is necessary because the utf8 view is not actually instantiated as … Read more
Update: As of Swift 4.2 (distributed with Xcode 10.1) there is a unified random API in the Swift standard library, see SE 0202 Random Unification. You can simply call UInt64.random(in: minValue … maxValue) to get a random number in the given range. (Previous answer for Swift < 4.2:) With arc4random_buf() you can create “arbitrary large” … Read more
You can also see that the link between the parent view and the custom class is broken (not visible anymore) which is a huge problem. I had the exact same issue with the app i’m working on actually, updating XCode from 5.xxx to 6.1. The workaround that worked for me was to remove the reference … Read more
Have a look at OS X Code Signing In Depth Beginning with OS X version 10.9.5, there will be changes in how OS X recognizes signed apps Structure your bundle according to the expectations for OS X version 10.9 or later: Only include signed code in directories that should contain signed code. Only include resources … Read more
In my case this issue (“found an unexpected mach-o header code 0x72613c21”) appeared after I’ve installed Crashlytics, Fabric. Somehow pods appeared to become an embedded binary. So I had to remove it, pod install once more, and the issue disappeared.
In Xcode6 for all devices splash screen you need to make splash image for each device size retina and non retina. Best way of done this thng use asset Catalog from target–>general like following screenshot: when you tap the right small arrow near of launchImage (->) you can see the following window: Currently there is … Read more
Only iOS 7.0 and later simulators are supported on Xcode 6.0.x and 6.1.x. Only iOS 7.1 and later simulators are supported on Xcode 6.2 and greater. The older simulators runtimes are not compatible with the new CoreSimulator architecture. You need to install Xcode 5.1.x if you want to run iOS 6.x simulators. The iOS 7.0 … Read more
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to ‘Ad-Hoc’ profile instead of ‘Production’ profile. Setting it back to ‘Production’ did the trick for me.
I’m having the same problem. Needed to put a build out last night. I ended up just reusing an old plist and updating it. Here’s a template: <?xml version=”1.0″ encoding=”UTF-8″?> <!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”> <plist version=”1.0″> <dict> <key>items</key> <array> <dict> <key>assets</key> <array> <dict> <key>kind</key> <string>software-package</string> <key>url</key> <string>[INSERT URL HERE]</string> </dict> </array> <key>metadata</key> … Read more
As usual when upgrading Xcode: Clean your build folder (Product -> (Alt key) -> Clean Build Folder) Clean project (Product -> Clean) Delete derived data Xcode < 6.3: Window -> Organizer -> Delete derived data Xcode >= 6.3: Window -> Projects (select project) -> Delete derived data Then try to build your project again.