Search results for

“build disappears”

51,310 results found

Post

Replies

Boosts

Views

Activity

JS closure causing odd behavior with JXA
I'm using JXA to build Cocoa applications and running into a strange issue when attempting to wrap all an app's JavaScript with an immediately-invoked function expression.What's the issue?If the code for an app with a single NSWindow is wrapped in an immediately-invoked function, the app's window will close on it's own without any type of application crash. The app stays running.Here's the code I'm using:(function() { ObjC.import(Cocoa); var styleMask = $.NSTitledWindowMask | $.NSClosableWindowMask | $.NSResizableWindowMask | $.NSMiniaturizableWindowMask; var window = $.NSWindow.alloc.initWithContentRectStyleMaskBackingDefer( $.NSMakeRect(0, 0, 800, 400), styleMask, $.NSBackingStoreBuffered, false ); window.center; window.title = 'NSWindow Closure Bug?'; window.makeKeyAndOrderFront(window); }());Here's the example application https://dl.dropboxusercontent.com/u/271215/jsclosurebugexample.zipor recreate it with- Script Editor > New- Copy/paste the above code- Save > File Format: Applicat
Topic: App & System Services SubTopic: Automation & Scripting Tags:
2
0
1.1k
Jun ’15
Reply to Cannot connect device running IOS 5.1.1
From the Xcode 7 Beta release notes (bold is mine)Xcode 7 has a ENABLE_BITCODE option to embed bitcode in apps, app extensions, and frameworks. The option is turned on by default for iOS and is mandatory for watchOS projects submitted to the store.Some compiler and linker options are not supported when bitcode is enabled (e.g., -mglobal-merge for clang and -sectalign for linker). Some linker options will result in warnings (e.g., - weak_framework and -weak_libraries). Bitcode builds for iOS also require a minimum deployment target of 6.0. (18447465)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jun ’15
Reply to Cannot connect device running IOS 5.1.1
Yes, I have the Enable Bitcode option switched off. I can build and run my app in the simulators, but I cannot connect hardware that's running less than iOS 6.0.I'm wondering whether running code (through the debugger) on hardware that has less than iOS 6.0 has been dropped, or whether it's only because it's a Beta.Regards,David
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jun ’15
Reply to Image not showing on iOS8
Set a breakpoint and inspect the value of your backgroundImage variable. If it contains a valid image, then you will have to look at whatever that KLPAAlert class is. It's not an Apple framework class so you probably won't get any support here.If the image is *not* loaded correctly, then you'll have to look at the build settings and make sure the filename matches exactly (including case), and that it's being copied to the app target in the Copy Bundle Resources build phase. (Or if it's in an asset catalog, make sure the name matches - you might not want that .png suffix.)
Topic: Programming Languages SubTopic: General Tags:
Jun ’15
Software keyboard performance degrades considerably after continuous use of our app built with Xcode 6
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
Topic: Developer Tools & Services SubTopic: Developer Forums Tags:
0
0
233
Jun ’15
Reply to Abort trap: 6
I'm continuing to test this and have found something interesting. At least in my case, the problem appears to have something to do with SceneKit's SCNVector3 type. Here's what I did.1. Create a brand-new project in Xcode 7 beta-1. Type is Game, Language is Swift, Game Technology is SceneKit.2. Build and run with default settings. Project builds and runs fine in simulator (you will see the default rotating 3D spaceship model).3. Add a single SCNVector3 property to the gamecontroller in GameViewController.swift, like this:class GameViewController: UIViewController { var p = SCNVector3ZeroLo and behold, guess who pops up? Our friend Abort trap: 6. Project will no longer compile.4. Change the constant to an empty initializer.class GameViewController: UIViewController { var p = SCNVector3()Same problem, Abort trap: 65. Remove property, restoring to the clean project state. Abort trap: 6 is gone, project again compiles and runs.6. Try adding SCNVector4 instead of SCNVector3.class GameViewControlle
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Jun ’15
Supporting the Enterprise with OS X Automation notes
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 (
Topic: App & System Services SubTopic: Core OS Tags:
0
0
2.7k
Jun ’15
Reply to "Abort trap: 6" error in Swift 2 with Xcode 7 beta-1
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 swift 0x000000010c
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’15
buttons and uipicker not visible on the view
I have create a new single view application and have added button and uipicker to the view howeve i cannot see the edges of the buttons and picker.Once I build and run the application i cannot see the uipicker on the iphone app. Please help and advise how to solve this issue.I using OS X Yosemite and XCode 6.3.2. Tried different iphone on the ios simulator but still not able to view correctly.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
281
Jun ’15
fatal compiler error: PCH
First attempt building our code base in xCode7 for iOS -- getting a fatal error in the backend running ProcessPCH++. I've included the output below.Is there any further diagnostic details we can turn on to provide information? This is a LARGE codebase, and the chances of me being able to supply it to Apple as-is is zero.COMPILER ERROR==============fatal error: error in backend: Broken module found, compilation aborted!clang: error: clang frontend command failed with exit code 70 (use -v to see invocation)Apple LLVM version 7.0.0 (clang-700.0.53)Target: arm-apple-darwin14.3.0Thread model: posixclang: note: diagnostic msg: PLEASE submit a bug report to http:/ and include the crash backtrace, preprocessed source, and associated run script.Command /Applications/Xcode_7.0-beta1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 11PCH CALL========ProcessPCH++ /Users/XXUSERXX/Library/Developer/Xcode/DerivedData/app-dkfbghqolkiziwhjwearcxydwgsm/Build/Inter
Topic: Developer Tools & Services SubTopic: General Tags:
2
0
2.6k
Jun ’15
JS closure causing odd behavior with JXA
I'm using JXA to build Cocoa applications and running into a strange issue when attempting to wrap all an app's JavaScript with an immediately-invoked function expression.What's the issue?If the code for an app with a single NSWindow is wrapped in an immediately-invoked function, the app's window will close on it's own without any type of application crash. The app stays running.Here's the code I'm using:(function() { ObjC.import(Cocoa); var styleMask = $.NSTitledWindowMask | $.NSClosableWindowMask | $.NSResizableWindowMask | $.NSMiniaturizableWindowMask; var window = $.NSWindow.alloc.initWithContentRectStyleMaskBackingDefer( $.NSMakeRect(0, 0, 800, 400), styleMask, $.NSBackingStoreBuffered, false ); window.center; window.title = 'NSWindow Closure Bug?'; window.makeKeyAndOrderFront(window); }());Here's the example application https://dl.dropboxusercontent.com/u/271215/jsclosurebugexample.zipor recreate it with- Script Editor > New- Copy/paste the above code- Save > File Format: Applicat
Topic: App & System Services SubTopic: Automation & Scripting Tags:
Replies
2
Boosts
0
Views
1.1k
Activity
Jun ’15
Reply to Cannot connect device running IOS 5.1.1
From the Xcode 7 Beta release notes (bold is mine)Xcode 7 has a ENABLE_BITCODE option to embed bitcode in apps, app extensions, and frameworks. The option is turned on by default for iOS and is mandatory for watchOS projects submitted to the store.Some compiler and linker options are not supported when bitcode is enabled (e.g., -mglobal-merge for clang and -sectalign for linker). Some linker options will result in warnings (e.g., - weak_framework and -weak_libraries). Bitcode builds for iOS also require a minimum deployment target of 6.0. (18447465)
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jun ’15
Reply to Cannot connect device running IOS 5.1.1
Yes, I have the Enable Bitcode option switched off. I can build and run my app in the simulators, but I cannot connect hardware that's running less than iOS 6.0.I'm wondering whether running code (through the debugger) on hardware that has less than iOS 6.0 has been dropped, or whether it's only because it's a Beta.Regards,David
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jun ’15
Reply to Watch Simulator not loading watchOS apps in 7 beta
I get this 95% of the time. To work around the bug, remove your iOS app from the Simulator and then build/run again.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jun ’15
Reply to How can I make a great document thumbnail?
Hmm. According to the WWDC15 presentation on UIDocument, building a document thumbnail using a UIView is a no no. So I have to create some facsimile of my document from scratch using other means. This is non-trivial.
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Jun ’15
Reply to Image not showing on iOS8
Set a breakpoint and inspect the value of your backgroundImage variable. If it contains a valid image, then you will have to look at whatever that KLPAAlert class is. It's not an Apple framework class so you probably won't get any support here.If the image is *not* loaded correctly, then you'll have to look at the build settings and make sure the filename matches exactly (including case), and that it's being copied to the app target in the Copy Bundle Resources build phase. (Or if it's in an asset catalog, make sure the name matches - you might not want that .png suffix.)
Topic: Programming Languages SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jun ’15
Software keyboard performance degrades considerably after continuous use of our app built with Xcode 6
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
Topic: Developer Tools & Services SubTopic: Developer Forums Tags:
Replies
0
Boosts
0
Views
233
Activity
Jun ’15
Reply to Abort trap: 6
I'm continuing to test this and have found something interesting. At least in my case, the problem appears to have something to do with SceneKit's SCNVector3 type. Here's what I did.1. Create a brand-new project in Xcode 7 beta-1. Type is Game, Language is Swift, Game Technology is SceneKit.2. Build and run with default settings. Project builds and runs fine in simulator (you will see the default rotating 3D spaceship model).3. Add a single SCNVector3 property to the gamecontroller in GameViewController.swift, like this:class GameViewController: UIViewController { var p = SCNVector3ZeroLo and behold, guess who pops up? Our friend Abort trap: 6. Project will no longer compile.4. Change the constant to an empty initializer.class GameViewController: UIViewController { var p = SCNVector3()Same problem, Abort trap: 65. Remove property, restoring to the clean project state. Abort trap: 6 is gone, project again compiles and runs.6. Try adding SCNVector4 instead of SCNVector3.class GameViewControlle
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jun ’15
Supporting the Enterprise with OS X Automation notes
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 (
Topic: App & System Services SubTopic: Core OS Tags:
Replies
0
Boosts
0
Views
2.7k
Activity
Jun ’15
Reply to iOS 9 battery life
iOS 9 battery usage by my measurements is reduced 62%. In addition overall performance is about 30% slower right now. I assume it's the beta build. iOS 8 was that way in the first couple of betas too.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jun ’15
Reply to "Abort trap: 6" error in Swift 2 with Xcode 7 beta-1
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 swift 0x000000010c
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Jun ’15
Reply to Swift is flagging the use of deprecated functions as errors
I don't know if the previous response answered your question. Check your project build settings under Apple LLVM 7.0 - Warning Policies that you do not have Treat Warnings as Errors enabled.
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Jun ’15
buttons and uipicker not visible on the view
I have create a new single view application and have added button and uipicker to the view howeve i cannot see the edges of the buttons and picker.Once I build and run the application i cannot see the uipicker on the iphone app. Please help and advise how to solve this issue.I using OS X Yosemite and XCode 6.3.2. Tried different iphone on the ios simulator but still not able to view correctly.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
281
Activity
Jun ’15
Reply to Swift 2.0 deployment target 7.1
I'm getting a similar thing when setting the target to 7.1.A bunch of the bitcode warnings disappeared by doing what @beagle said but I'm still getting the exception on the swift-stdlib-tool
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jun ’15
fatal compiler error: PCH
First attempt building our code base in xCode7 for iOS -- getting a fatal error in the backend running ProcessPCH++. I've included the output below.Is there any further diagnostic details we can turn on to provide information? This is a LARGE codebase, and the chances of me being able to supply it to Apple as-is is zero.COMPILER ERROR==============fatal error: error in backend: Broken module found, compilation aborted!clang: error: clang frontend command failed with exit code 70 (use -v to see invocation)Apple LLVM version 7.0.0 (clang-700.0.53)Target: arm-apple-darwin14.3.0Thread model: posixclang: note: diagnostic msg: PLEASE submit a bug report to http:/ and include the crash backtrace, preprocessed source, and associated run script.Command /Applications/Xcode_7.0-beta1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 11PCH CALL========ProcessPCH++ /Users/XXUSERXX/Library/Developer/Xcode/DerivedData/app-dkfbghqolkiziwhjwearcxydwgsm/Build/Inter
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
2
Boosts
0
Views
2.6k
Activity
Jun ’15