Looks like Xcode 7 really wants us to include a launch screen storyboard/XIB, even if you've created launch images for all devices/orientations. That would be great, except I can't figure out how to get the right look for my app.My app is extremely simple. It has a single toolbar located at the bottom of the screen, and a navigation bar at the top. I can get the toolbar to look right, but I can't get the nav bar to work. You can't embed the view controller inside a navigation controller. I tried placing a nav bar in the scene and set it to align at the top under the status bar, but then the status bar background is left white when it should be the nav bar color.How do you do this?
Search results for
Xcode
92,318 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Playgrounds are slow, and in my opinion, basically unusable in the current Xcode 7 beta. 😢
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Check the console output. If this is an Xcode 6 playground, show the assitant editor to see the console output. There may be an error there.Also, please post your playground code - it's very difficult to guess what might be wrong without seeing it.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Did you update the project for Xcode 7? If so, try editing the source of the playground (see the xml metadata) to bring it up to date.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Anything from the Xcode 7 b releases notes shed light?Playgrounds Opening a Playground that was previously displaying the Version Editor may present an alert stating, “The file “MyPlayground.playground” couldn’t be opened because you don’t have permission to viewit.” (20623808). Workaround: Dismiss the alert dialog and show the Standard Editor (Command-Return).Playgrounds sometimes show a window with no editor if they are opened as part of Xcode launching (20694143) Workaround: Close and re-open the playground.Executing an iOS Playground for the first time may take longer than subsequent executions. (21163503)For old-style playgrounds, the menu item Edit->Convert->To Latest Swift Syntax... is greyed out. (20902099) Workaround: Upgrade the playground before attempting to convert to Swift 2.0 by choosing Editor- >Upgrade Playground...Playground pages may recompile each time they are navigated to, even when there are no changes. (21177662)Playgrounds live views may not show images when
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
There is info in the documentation for XCode you can get to by going to the Help menu and choosing Documentation and API ReferenceIn the pane on the left, choose XCode 7 Documentation > XCode > IDE's > Guides > AutoLayout HelpOr, the online version:https://developer.apple.com/library/prerelease/ios/recipes/xcode_help-IB_auto_layout/chapters/UnderstandingAutolayout.htmlSpecifically:https://developer.apple.com/library/prerelease/ios/recipes/xcode_help-IB_auto_layout/chapters/pin-constraints.html#//apple_ref/doc/uid/TP40014226-CH28-SW1
Topic:
Programming Languages
SubTopic:
Swift
Tags:
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
I am developing a new update to my app, AnyTrail, using Xcode 7 with Base SDK of iOS 9. But when I try to archive the app, there are warnings like Ignoring debug info with an invalid version (3), and error which says Command failed due to signal: Abort trap: 6 which prevents me from successfully archiving the app. Why is there this error? Is it because I can't submit updates that have a Base SDK of iOS 9 when that operating system is still in beta? Or is it an Xcode bug? Thanks!
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 GameViewController: UIView
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Hello, I have gotten this error that prevents my project from compiling, and others have reported it as well in various places. My project is Swift with SceneKit, migrated from 6.3.X to 7, but I have also been able to reproduce it with a fresh project created in Xcode 7 beta-1. If you are having this problem, please see this discussion for details:https://forums.developer.apple.com/message/10714I am starting a thread here in the Swift forum because it seems the issue is Swift-specific (and possibly SceneKit-specific as well) and this is a more active forum. If we can some more discussion and testing, we can start submitting bug reports on this, but I would like to gather more information from other users before I do that to narrow down the problem.
Just curious, are you using Swift 2 with SceneKit by any chance?If so, please see these discussions:Abort trap: 6 error in Swift 2 with Xcode 7 beta-1Abort trap: 6
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
My first app was recently approved by Apple, and want to add in-app purchase. should i create a brand new xcode project that includes everything plus the new features? or should i just use the old project and just add the new features there? what is the execution overview on this?
Ah thanks. So pin means the add new constraits button.But what changed there? It works just as in Xcode 6.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Same here - cannot access remote Git repository. Plus, when I go into Xcode 7 Preferences -> Accounts, the repository entries that existed for my projects under Xcode 6.3.2 are either corrupted or not present, and, if I so much as select any of them, Xcode 7 crashes.Have not tried a clean install of Xcode 7 as I both of my development machines have 6.3.2 installed.I think we are stuck waiting for a fix. I have submitted a bug report, however.
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/IRGenSI
Topic:
Programming Languages
SubTopic:
Swift
Tags: