Hi all,I am trying to create a standalone Mac OS X application with Python (py2app) using an example code, which worked on Yosemite.On El Capitan Beta 1 and Beta 2, no minimal demo app seems to work any longer.# python setup.py py2app -Arunning py2appcreating /Users/bluedot/build/bdist.macosx-10.11-intel/python2.7-standalone/appcreating /Users/bluedot/build/bdist.macosx-10.11-intel/python2.7-standalone/app/collectcreating /Users/bluedot/build/bdist.macosx-10.11-intel/python2.7-standalone/app/tempcreating build/bdist.macosx-10.11-intel/python2.7-standalone/app/lib-dynloadcreating build/bdist.macosx-10.11-intel/python2.7-standalone/app/Frameworks*** creating application bundle: MyApp ***error: /Users/bluedot/dist/MyApp.app/Contents/MacOS/MyApp: Operation not permittedsetup.py:from setuptools import setupAPP = ['MyApp.py']DATA_FILES = []py2app_options=dict()setup( app=APP, data_files=DATA_FILES, options=dict(py2app=py2app_options), setup_requires=['py2app'],)MyApp.py:
Search results for
build disappears
49,347 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I'm building up a set of Complications and have come to the CLKComplicationTemplateUtilitarianLargeFlat which only has one textProvider.I want to display some text, along with a relative date. So I tried doing this:let date = CLKRelativeDateTextProvider(date: NSDate(), style: style, units: units) let template = CLKComplicationTemplateUtilitarianLargeFlat() template.textProvider = CLKSimpleTextProvider(text: next: (date))But all I get is:<CLKRelativeDateTextProvider: 0x79860b80>Can you extract the raw text from the CLKRelativeDateTextProvider (or any provider for that matter)? Or combine providers?
As it was mentioned in the keynote I added a new Watch OS 2.0 target to my project. I copied all the files, storyboard objects and resources to the new watch app and watch app extension folders. The targets for the files are set correctly. Then I deleted the old target with all the files.First problem that occured was the bundle identifier. The compiler told me now that the watch app bundle identifier must be a prefix of the extensions bundle identifier. In my WatchKit 1.0 app I used two bundle identifiers like x.y.z.watchapp and x.y.z.watchkitextension. But now it seems that this does not work anymore so I created a new AppID with x.y.z.watchapp.extension as a new bundle identifier.But now I get another compliler error and really dont know how to fix it. Maybe someone can help me.error: WatchKit App doesn't contain any WatchKit Extensions whose WKAppBundleIdentifier matches x.y.z.watchapp. Verify that the value of WKAppBundleIdentifier in your WatchKit Extension's Info.plist matches the value of CFBundleIden
I am trying to use Xcode (v6.3.2) to debug my C++ command line application. I have setup an external build target that calls `make` and successfully builds my application. I have also modified the Run scheme to run the built application and `debug executable` is checked and `Build Configuration` is set to `Debug`.However, no matter what I do, I cannot get any breakpoint to trigger when I run. The application always runs successfully but just doesn't stop at any of the breakpoints.This seems to be a very common issue and I have tried several of the suggestions that people have made over the years. One of the most common solutions I have read is to disable the Load symbols lazily setting under Preferences -> Debugging. However, this setting no longer seems to exist for the latest version of Xcode. I have also created an .lldbinit file with the setting as described at this URL: http://lldb.llvm.org/troubleshooting.html. The breakpoints are enabled. In my `Makefile`, the compiler is
Thank you Dirk. The attribute was inside the NSExtension dictionary. I have overseen it. Now the project builds 🙂
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I'm still not able to see the OTA update for my 6 plus. I checked the version I have and it does not match the newest build code. I'll keep checking each day then use the Mac when I get home if it's still broken
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Or, is this a case where it will still be there for legacy apps, but if I target iOS 9 for my builds, I can't use OpenAL? It was still there on the audio slides from WWDC 2015.Anyone have any more information? Looks like I may spend my Christmas vacation moving all my apps to AVAudioEngine.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
What build are you running? Please file a bug report and if you can include a sample project that would be great.
Topic:
App & System Services
SubTopic:
General
Tags:
Watching the Building Better Apps with Value Types in Swift WWDC video, and got to the part where he talks about the Sieve of Eratosthenes routine. Thought I'd plug it into a playground:func primes(n: Int) -> [Int] { var numbers = [Int](2..<n) for i in 0..<n-2 { guard let prime = numbers[i] where prime > 0 else {continue} for multiple in stride(from: 2 * prime*2,to: n-2, by: prime) { numbers[multiple] = 0 } } return numbers.filter { $0 > 0 } }But on the line with the guard statement, I'm getting an error:initializer for conditional binding must have Optional type, not 'Int'Is this not allowed? I know an 'if let' has to have an optional, but I thought a 'guard' didn't need one?Thanks.
If you hold down the option key, the Clean menu item (in the Product menu) turns into Clean Build Folder....It might get whatever cached data was causing the issue, that Clean misses (particularly if you have multiple interdependant projects in your workspace).
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I'm seeing the same thing - no crashes for TestFlight builds at all. In fact, I actually have no crashes showing up Xcode at all of any kind.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I managed to reproduce this in a test project, so I'm now wondering if this is intended behaviour and all of my other table views are somehow preventing it becuase of the various custom classes I use (even though I'm using the same custom classes in my app for the tables affected). Anyway, here's a sample project showing the issue if anyone has time to take a look:http://literatureandlatte.com/misc/TableEditBugTest.zipSimply download, build and run, then click into the rows. Clicking on the text area of a row causes editing to start immediately, regardless of whether row was already selected or not; clicking to the right of the text causes expected behaviour, with the row just being selected. This behaviour only occurs when -setDoubleAction: is set and the text field in the table cell is set to be editable.
Topic:
UI Frameworks
SubTopic:
AppKit
Tags:
More details:I restarted the 10.10.3 system. The bug remained. I deleted the playground from the project, quit Xcode, reopened Xcode, and added a playground to it. “Hello playground” executed. I then typedfncwhich is what the profession calls a “typo.” The console displayed the syntax error, and the alert complaining about the missing target executable returned. It recurred every minute or so for as long as the playground was visible. Correcting the typo and filling out the one-line function did not relieve the issue.Also, the insertion point would periodically jump to the first character in the editor, and whatever I’d typed in the previous 10 seconds or so disappeared. Maybe that’s another manifestation of the same bug, maybe not.Sounds like bug-report time, and no live experimentation with Swift 2.0 for another 2 weeks (the probable date for beta 3).
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Our application was submitted to Apple as version 1.0.0 and approved for release.We however found an issue before releasing that caused us to decide cancel the release. We are now ready to submit the build again to Apple.Since we never released 1.0.0 should we up version the build to 1.0.1 before submitting to Apple?
> OK, I think I am still a bit confused about this. It sounds like you are> saying that there is no way for the phone and watch to share a keychain with> accessGroup.>Yes, that's correct.> This would seem to imply that the user would have to log into each the> watch and the phone separately for the same app, that seems wrong.>Yes, that's correct. The phone and watch apps can now be completelyindependant entities with their own login credentials. You can leverage thephone app to improve the onboard-ing process for the watch app, butfundamentally they are independant devices with their own data stores.> However, I don't see any other way to securely do this if the keychain> can't be shared. Am I missing something? Sorry for the confusion....>You'll need to build your own authentication infrastructure here. My firstpass advice would be to have your phone app log into your service and generateyour authentication token to use for future communication (the same way mostmodern
Topic:
App & System Services
SubTopic:
General
Tags: