Updated an app to iOS 9 / Swift 2 / watchOS 2 and since then, Xcode claims it can't find my embedded framework when building the watchOS extension. It has no issues finding it for my iOS app and the build settings look ok - the framework is showing as a dependency... but yeah, no dice. Tried cleaning and nuking Derived Data.Any ideas?
Search results for
xcode github
91,937 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
i created a simple test app using the watch app Xcode template in Xcode 7. when i build and run this on the watch simulator, the app never runs. When i try to run the same app on the device (also via Xcode), the app gets installed but never runs. Looking at the watch logs, at appears that nanoappregistryd crashes on the watch right around the same time. sometimes, the watch actually reboots when this happens.Has anyone been able to debug a watchOS 2.0 app via Xcode7?ps: iPhone is on iOS9 and mac is on OSX El Capitan
Check the Target Platform of your framework and watchkit extensiosn in their Build Settings.It seems currently Xcode 7 only lets you choose either iOS or watchOS, but since your framework is shared between platforms you need to manually put all 4 of: watchsimulator, watchos, iphonesimulator, iphoneosIn my case, after fixing the above, I also needed to add armv7k and i386 to Valid Architectures.Then I finally got to see all the new WatchKit compile errors 🙂
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Network securityHTTPS, TLSIn 2015, TLS is a minimum baselineMany servers default to TLSv1.0, from 1999Newest version is TLSv1.2TLSv1.2 is not enough. Compromise of a server key lets you decrypt all TLS traffic that was encrypted in the past.With forward secrecy, a server key compromise will only let you read future traffic. Past traffic will not be able to be decrypted.By default, apps linked against iOS 9 and OS X 10.11 cannot make unprotected HTTP connections.TLS connections will need to comply with best practices- Exceptions can be declared on a case-by-case basis in your app's Info.plist file.System Integrity ProtectionDefense in DepthSecurity is about layersOne layer failing shouldn't defeat all securityRely on multiple layers of protectionDelay the attackerReduce your attack surfaceSeque into talking about Vauban and star fortresses. History lesson FTW.OS X's star fortress security model:Outermost line - Developer ID and GatekeeperSecond layer - Sandbox - attacker only gets access to t
Hi all! I have some confusion about the new dev program. Now that everything is combined, do I still get access to XCode? I saw that it says on the Xcode 7 beta page that I can get the beta for free, but the developer plan says that I need to buy the plan to get access to software betas. I have no money to buy a plan, so I am stuck. I do not know what to do. Just as I was beginning to learn Swift and Objective-C, Apple takes away my ability to develop for free. Is there even free access after my safari plan expires on July 8th?
I've updated the app for watchOS 2 using the built in suggestion with Xcode 7 when you first build it. I've changed all the necessary code so there's no errors or warnings but I can't seem to run either the containing app or the watch app in the simulator; they never launch but they do copy over to the simulators.Is there a new scheme I should be using? I'm using the previous scheme for the main watch app which now automatically lets you choose between running the iPhone 6 simulator with either the 38mm or 42mm watch simulator.
Over the course of Swift's existence I've had to take advantage of a number of workarounds (i.e., hacks) to compile a Swift framework that utilizes non-modular system code, e.g., CommonCrypto, sqlite3, etc.These solutions have included:Renaming the umbrella header to be something different than the module name in order to exploit a bug that let frameworks compile with bridging headers, wherein the non-modular import happened: #import <CommonCrypto/CommonCrypto.h>Building a dummy, optional framework with a custom module map specifying the absolute path to an SDK header (relative SDK paths don't work): module CommonCrypto [system] [extern_c] { header /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/include/CommonCrypto/CommonCrypto.h export * }Specifying a custom module map with an additional header specifying the absolute path to an SDK header: framework module MyCrypto { umbrella header MyCrypto.h header /Applications/Xcode.app/Contents/Developer/Pla
When I try to run the watchkit app, it success, but didnt run at all, and I'm even not able to install the app on watch simulator. When I try to use my own phone and watch, it says: unknown errer happens.Does anyone know how to solve this?
I've downloaded Xcode 7 beta, mounted the dmg, and copied it to Applications. When I attempt to run, I get this alert:“Xcode-beta” is damaged and can’t be opened. You should move it to the Trash.So I trash the app and the dmg, then repeat. I've done this maybe 5 times now and it never does work.How can I resolve this? I'm running 10.11.
Yes, with something like this ...xcodebuild test -scheme YourAppScheme -destination platform=iOS Simulator,OS=9.0,name=iPhone 6Replace your project's scheme name in for 'YourAppScheme'Used to be you had to export/share the scheme (go to manage schemes in Xcode) to get this to work. Not sure if that is still the case. Just a warning.You can play with the destination settings to pick different devices, etc.Cheers.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
It is most likely an issue with Gatekeeper. I have seen this exact situation before with prevoius beta releases. To fix, go to Preferences > Security & Privacy, click the lock in the bottom left and enter your password, then click on Allow apps downloaded from anywhere. Next, right-click on the XCode 7 beta in your applications folder, and click open. A warning will come up, click on open in that dialog. This will add an exception to Gatekeeper. You can now go back into preferences and set your Allow apps from... back to your previous setting, and Xcode 7 will now open from launchpad like usual.Hope this helps!
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I am working on an App where after the user completes the Revert to Saved… time machine like dialog the system sends a bunch of error messages to the XCode console:Jun 9 20:16:52 BDM-2.local Mandelbrot[36183] <Error>: CGContextClipToRects: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.Jun 9 20:16:52 BDM-2.local Mandelbrot[36183] <Error>: CGContextSetFillColorWithColor: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update....None of these graphics commands are part of my code. The d
Does xcode have a goal seek function like excel? I've been searching but found nothing but figured I should double check here.
Whether you can get the beta or not, you can certainly download the release version of Xcode for free from the Mac App Store.I believe the intention was that the betas would also be free but I'm not 100% sure on that. You might have to re-watch the keynote to see what they said. It's also possible some links are not working yet. Xcode 7 is still pretty new.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
As noted, you can always download Xcode via the Mac App Store. What's changed is that now, you can test your app on your own device without having to pay for a Developer Account.Another change is that for one fee (USD$99), you now have access to iOS, Mac OS and WatchOS app development and distribution.They said during the keynote that public betas will continue and be available later, but if you want access now/early, you need to be in a paid program.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: