Our app records data for filling out reports. After continuously entering data, the appearance and disappearance of the software keyboard slows down considerably, making the app unusable.This occurs when the ipa file is built with Xcode 6 (SDK 8.3). If we build the ipa file with the same code in Xcode 5 (SDK 7.1), the problem does not occur.When app is experiencing the performance issues, they immediately go away if we connect a hardware keyboard through bluetooth, and come back when we disconnect the keyboard. This is how we determined that it was the actual keyboard and not just when the text field receives focus.The issue occurs whether we are using the default iOS keyboard or a third party keyboard.This issue is occurring in the version of the app that is currently available in the app store, so it wasn't rejected by the app reviewers.We have profiled the code using Time instrument. We see _CfxNotificationPost growing. The response to keyboard events start at 17ms, 120ms, 300ms, 900ms fo
Search results for
dsym file
77,678 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
If you look at Apple's header files, it looks like they use the NS_DEPRECATED macro from NSObjCRuntime.h.Does it have the same effect as __deprecated?
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I literally just filed a radar about this. It's very annoying. I usually go to developer.apple.com/membercenter/ and log in there, then come back to the forums.
Topic:
Developer Tools & Services
SubTopic:
Developer Forums
Tags:
Enterprises are made up of individual people.- When you're building solutions, keep in mind that you're building your tools for peoples' benefit.Workflow strategiesTake advantage of strengthsUse the right tool for the job you're working onIf all you have is a hammer, all your problems look like nails.In reality, only part of the problems you're trying to solve will be nails.Make your workflow modularDesign your workflows so that different modules are being connected together to do the job.Enable repurposing, adaptation and expansion.Code re-use is a good thing.Optimize your workflowProblems will always appear in a enterprise workflow. Anticipate the issues and optimize your automated solution's workflowsEliminate bottlenecksReduce repetitionRemove complexity / confusionDesign your workflows for your usersPeople will avoid complex solutions, they won't like using them if they're hard to understand or operate.People will use convenient solutions, all the time.Pursue inclusionSuccess uses AND (inclusion) conditi
So was able to get some results. Using the following code from above:if let audioURL = NSBundle.mainBundle().URLForResource(Audio/Beep5, withExtension: caf) { let asset = WKAudioFileAsset(URL: audioURL) let playerItem = WKAudioFilePlayerItem(asset: asset) let player = WKAudioFilePlayer(playerItem: playerItem) switch player.status { case WKAudioFilePlayerStatus.ReadyToPlay: player.play() case WKAudioFilePlayerStatus.Failed: print(player.error) case WKAudioFilePlayerStatus.Unknown: print(unknown) player.play() } }BUT, it doesn't work on the simulator and on the device itself it does require the watch be paired with a bluetooth speaker (which I think defeats the purpose). Not only that, it doesn't work 100% either. I have an app with about 20 different sounds and maybe one or two play correctly about 20% of the time. The reason I can hear hissing on the speaker but no sounds. All my files are mp3, and I haven't tried any other format. But might write another test app to try it out.I think we need to loo
Topic:
App & System Services
SubTopic:
Core OS
Tags:
As I posted in the other thread, I think the Abort Trap: 6 error during compile is the result of failed assertions in the Swift compiler. and different bugs could be causing different assertions to fail but generate the same overall error.They may have the same underlying cause, but your SCNVector3 issue is triggering this assertion:Assertion failed: ((IGF.IGM.DataLayout.getTypeSizeInBits(coercionTy) == IGF.IGM.DataLayout.getTypeSizeInBits(paramTI.StorageType)) && Coerced types should not differ in size!), function emitDirectExternalParameter, file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/IRGen/IRGenSIL.cpp, line 908.and mmuszynski's code is triggering this one:Assertion failed: (gen.getTypeLowering(result.getType()).isTrivial() && nontrivial result is returned unowned?!), function emitObjCReturnValue, file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/SILGen/SILGenBridging.cpp, line 649. I think y
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I filed a bug report based on my own situation. Hopefully more people will submit bug reports and Apple will coalesce them. Here's the info:Bug ID: 21376523Title: Adding property of type SCNVector3 yields Abort trap: 6 errorClassification: Serious BugReproducibility: AlwaysDescription:When using Swift 2 with Xcode 7 beta-1 (7A120f), with SceneKit, using SCNVector3 produces Abort trap: 6 compile error. This happens whether a project is migrated from (Swift 1.2 + Xcode 6.3) to (Swift 2 + Xcode 7.0), or with a fresh Swift 2 + Xcode 7.0 project. Error text is below:------------------[COMMAND LINE COMPILER OPTIONS OMITTED BECAUSE OF 3,000 WORD BUG REPORT LIMIT]Assertion failed: ((IGF.IGM.DataLayout.getTypeSizeInBits(coercionTy) == IGF.IGM.DataLayout.getTypeSizeInBits(paramTI.StorageType)) && Coerced types should not differ in size!), function emitDirectExternalParameter, file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/IRGen/IRGenSIL.cpp, line 908.0
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Ah, interesting. Well it seems like it's a broad enough problem that it will probably get fixed soon, but you never know. I encourage people to file bug reports anyway (I did, copied in the Swift forum thread).
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
This seems to be in conflict with the following statement by Apple:Get your apps ready with the latest beta versions of the San Francisco fonts for iOS 9,OS X El Capitan, and watchOS 2.Found here: https://developer.apple.com/fonts/I was able to download the fonts from the page above. So I am not sure about the source KMT's post and whether is is against the HIG or something for an iOS 9 app? It appears that the post from KMT is from here:https://developer.apple.com/watch/human-interface-guidelines/resources/And it looks like it pertains to resources for WatchOS downloads. But if you download the SF Fonts from the above link, then the Apple License Agreement with with files says this:APPLE INC.LICENSE AGREEMENT FOR THE APPLE SAN FRANCISCO FONTFor iOS and OS X application uses only---So it looks like you can use it with an iOS app and this article seems to confirm that:http://appleinsider.com/articles/15/06/12/apple-releases-san-francisco-system-fonts-for-ios-os-x-and-watchos-2-to-developersThe Font To
Topic:
App & System Services
SubTopic:
General
Tags:
Feel free to file a bug/feature request if you'd like an alternate access path.My money is on it being over the horizon, if at all, as far as us avg. devs are concerned.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
>it just refers to the fact that the compilers/OS will stop supporting non-ARC code after 10.11.Actually, it screams current bugs/coming changes, which is dead on the mark, I think by confirming the problems you've alluded to. File them to let Apple know, as usual.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Interesting. Thank you for clarifying that ckhpdx. Yeah, it seems filing a bug would be appropriate. Would be interested in knowing the appropriate way to indicate deprecation in Swift. I have also always used the __deprecated annotation in Objective-C code and have not had a need yet in my Swift code.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
As far as I can see, there is nothing wrong with your code. NSFetchRequest resolveEntityWithContext: (called by NSManagedObjectContext executeFetchRequest:error:) throws an Objective-C exception instead of making executeFetchRequest:error: return nil. You cannot catch Objective-C exceptions in Swift, so there is nothing you can do (except file a bug report).
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Have same problem here. But not only outlets don't connect. Assistant editor stops to work properly. I try to delete reference to my class and add it again. I try to delete drived data, clean project, restart xcode, restart OSX, restart computer, whole univers! That didn't works. Then i make another user and voila! It's start to work again! Outlets connects, assistant editor edits, univers spinning round'n'round. I decide that is files permissions problem an try to repair permissions for my current user. But that didn't works again. Is anybody else has this kind of problem? And solutions of cours!
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
What you may not grasp is that Cocoa's traditional error handling rules are still in effect:If a method fails and there's only really one failure case for it (trying to convert a non-numeric string to a number, etc.), the method returns nil or false.If an operation fails because of some complex issue with the current state of the computer (no such file, Wi-Fi turned off, etc.), the method emits an NSError. In Swift, NSErrors are handled with the do/try/catch mechanism.If an operation fails because the programmer wrote code that did something invalid (out-of-range array index, etc.), the method fails an assertion or raises an exception, which you should generally allow to crash your app. In Swift, it's not possible to catch exceptions.Creating a fetch request with an inaccurate entity name falls into that third category: failures that can only be the result of programmer error. Such problems are still handled by failing an assertion and crashing your app.
Topic:
Programming Languages
SubTopic:
Swift
Tags: