Search results for

build disappears

49,319 results found

Post

Replies

Boosts

Views

Activity

Reply to WatchOS 2 b2 - Xcode b2 "no symbols for paired Apple Watch"
I have a simmilar problem.When I connect my iPhone, Xcode has a status line saying it is installing the symbols for the Watch.The text then disappears and my iPhone becomes inaligible for debuging WatchKit extentions due to lack of symbols(iPhone 5s with iOS 9 - Beta 2 , Xcode 7 - Beta 2, Watch OS 2.0 - 13S5255d)I decided to run Xcode from command line for possible error traces. It seems that my Xcode is unable to download and mount a file called 'Watch1_1_13S5255d.dmg'. First URL returns 404 and the second URL which is done with my (Admin) team accounts fails with 403.Perhaps you should too open terminal, run/Applications/Xcode-beta.app/Contents/MacOS/Xcodethen connect your device and see the tracesBelow is a trace from my Xcode:2015-06-24 14:03:47.849 Xcode[28881:241044] Unable to mount DeveloperDiskImage on Doron's Apple Watch 2015-06-24 14:03:51.189 Xcode[28881:241027] Unable to mount DeveloperDiskImage on Doron's Apple Watch 2015-06-24 14:03:54.494 Xcode[28881:241047] DVTDownloadable: Download F
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’15
xCode Server sometimes picks up wrong target when building test scheme
Hello everyone,We want to use xCode Server to run automated tests, and we encouter a problem here. xCode Server picks up wrong target when it builds the test scheme.Here is the details. We have three targets, call it OurApp, OurApp-ent, and AutomatedTests. The AutomatedTests target is a test target with host application being set to OurApp. A scheme called AutomatedTests is created based on the AutomatedTests target. So this scheme SHOULD only depend on the OurApp target and it should NOT depend on OurApp-ent target. If we build or run this AutomatedTests scheme within xCode, it works fine. It builds only the AutomatedTests target and the OurApp target.Then we create a Bot based on this AutomatedTests scheme. Then we have trouble. Sometimes xCode Server just builds the OurApp and AutomatedTests targets. This is correct. But SOMETIMES, xCode Server decides to build the OurApp-ent target as well, without any change in the source code or the settings! And this will fa
2
0
436
Jun ’15
locationManager:didUpdateLocations Xcode7 Beta2
I cannot compile my project because of this error which I don't understand. It is an optional method on CLLocationManagerDelegate in a class defined like this:final class LocationManager: NSObject, CLLocationManagerDelegate {I tried other optional methods, no complains from the compiler. What is this about?This is the method: func locationManager(manager: CLLocationManager, didUpdateLocations locations: [CLLocation]) { }And this is the error:Objective-C method 'locationManager:didUpdateLocations:' provided by method 'locationManager(_:didUpdateLocations:)' conflicts with optional requirement method 'locationManager(_:didUpdateLocations:)' in protocol 'CLLocationManagerDelegate'It occurs when building WatchKit Extension.
1
0
1.7k
Jun ’15
MTLInitializeInterpose
I'm getting the following error..------------------------------------------------------------2015-06-24 10:57:50.715 Metal_Touch2[472:68884] Metal GPU Frame Capture Enabled2015-06-24 10:57:50.717 Metal_Touch2[472:68884]failed assertion _interposeHandle != NULL at/BuildRoot/Library/Caches/com.apple.xbs/Sources/Metal/Metal-54.7/Framework/MTLDevice.mm:110 MTLInitializeInterpose(lldb)this happens when i first call. self.device = MTLCreateSystemDefaultDevice()------------------------------------------------------------I developed this app using Xcode 6 - it is written in Swift & Metal.I upgraded to El CapitanI upgraded to Xcode 7 BetaI recompiled (now Swift 2.0) all my programs and tested on my iPad Air (Model 1474)targeting iOS 8.3 - all work fine. [this includes 25 applications using 35 different shaders]------------------------------------------------------------I installed the iOS 9 beta 2 software.[iOS 9 beta 2 - iPad Air (Model A1474) - 13A4280e]Still targeting iOS 8.3 my application builds and
12
0
2.3k
Jun ’15
Reply to Does Xcode 6.3.2 work on 10.11 beta 2?
That is correct. El Capitan, Xcode 7, iOS 9, Watch OS 2 are all beta, pre-release, developer preview, not ready for prime time, not released yet. You cannot build production code with them until they are officially released.If you need to go to production before they are released, then you need a completely separate stable production environment for your builds. This has always been the case. It would make no sense whatsoever for Apple to allow production code to be built with buggy pre-release tools.
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’15
Reply to Does Xcode 6.3.2 work on 10.11 beta 2?
Going to production with a build from the beta toolchain is obviously a bad idea. But that is very different from outright disallowing Xcode < 7 to run on El Capitan.I know in my case we have a stable build machine, but several developers are on the beta tools so we can get a jump start to finding/fixing bugs. In our case this change does nothing to protect against builds being submitted with beta tools (since we wouldn't have done that anyway) and makes active testing against those tools that much less likely to get done properly. Seems like a lose-lose to me.
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’15
in app purchases
I'm building an application in which users can create content and then that content is sold to other users. From the guidelines it would appear that I would need to use in app purchases for this. I'm not aware though of any way to just create in app purchase products on the fly from within the application after it's already on the store. Does anyone have any thoughts?Much appreciated.
3
0
1.2k
Jun ’15
Unable to create a bot with Xcode 7
Using Xcode Server b1 with Xcode 7 b1I get to a screen with the label Test with: followed by the word Loading in a disabled dop down menu.When I uncheck Perform Test Action on the previous screen, it changes to Build For: with the same disabled drop down menu.can anyone confirm this has been fixed in b2?
0
0
164
Jun ’15
WatchOS B2 version number
Interestingly, I wanted to see if anyone else can confirm their B2 version number. In the download listing it as Build: 13S5255c However, when I updated my watch it lists Build: 13S5255d Others seeing this? Still having navigation issues as well, most other core functions are working well.
1
0
324
Jun ’15
Can I build an Unity3D game without provisioning profile?
I bade a build in Unity3d and I get an Xcode project. I open the project and it ask me for a provisioning profile certificate. To make one, I need to register an iOS device in the member center (wich I don't have!) so, can I build with that provisioning certificate? Or can I use an iOS emulator to build it (is legal?)? If not, wich is the legal way to achieve this? Buy an iPhone/iPad?Thanks!
0
0
685
Jun ’15
ERROR ITMS-90087, ERROR ITMS-90209, ERROR ITMS-90125, WARNING ITMS-90080
I'm receiving the following errors and warning when uploading my archive to iTunes Connect via Xcode. There appears to be an issue with the embedded framework. I've run out of ideas on what exactly is causing the issue. Any ideas?ERROR ITMS-90087: “Unsupported Architectures. The executable for zulily.app/Frameworks/ChasePaymentech.framework contains unsupported architectures ‘[x86_64, i386]’.”ERROR ITMS-90209: “Invalid Segment Alignment. The app binary at ‘zulily.app/Frameworks/ChasePaymentech.framework/ChasePaymentech’ does not have proper segment alignment. Try rebuilding the app with the latest Xcode version.”ERROR ITMS-90125: “The binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple’s linker.”WARNING ITMS-90080: “The executable ‘Payload/zulily.app/Frameworks/ChasePaymentech.framework’ is not a Position Independent Executable. Please ensure that your build
5
0
9.1k
Jun ’15
Code signing issue: "obsolete resource envelope"
Hi all,I have a Developer ID app (that is not sandboxed), which I have built, archived & exported for Developer ID successfully many times. When I tried to archive & export the latest version, then check the resulting app viaspctl --verbose=4 --assess --type execute /path/to/my.appI am getting the error:rejected source=obsolete resource envelopeI can't figure out what has changed, and how to diagnose it or fix it. The app has many bundles and helpers, all of which appear to be signed when exporting. I am building on 10.10.3 using Xcode 6.3.2.Building, archiving & exporting another Developer ID app works correctly, so it seems like it must be something specific to that first app.Any clues?
4
0
3.8k
Jun ’15