#bwtoolkit

ibtool --remove-plugin-dependencies --write MainMenu.xib.new --plugin ~/Downloads/BWToolkit/BWToolkit.ibplugin MainMenu.xib

I spent a few hours over the last 2 days dealing with a new check Apple is doing when submitting apps to iTunesConnect through XCode/Organizer. What was just fine a month ago seems not anymore, as I was surprised when my app passed validation, but was rejected after upload with an email like this:

Unsupported Architecture - Application executables may support either or both of the Intel architectures:

i386 (32-bit)

x86_64 (64-bit)

I went to my build settings and confirmed that i386 and x86_64 were what were selected, and I even confirmed that my app binary was set to that by running "lipo -info MyAppBinary". 

My problem (after some pointers from @eternalstorms) was that I was using a couple third party frameworks in my app that still had PPC architecture inside their binaries. (ShortcutRecorder and BWToolkit). I attempted what I thought should have worked, and just ran "lipo -remove {ppcarchIDs} {frameworkbinary} -output {newFrameworkBinary}", which didn't work; also ran "ditto" to strip out the unwanted architectures - no go. 

Ended up having to recompile both frameworks from source, after ensuring "i386 x86_64" were the only architectures in the build settings. And now I'm fine. 

I recently forked BWToolKit to make it conform with the Mac App Store guidelines. The current version comes with an element called BWTokenField, which uses NSTokenAttachmentCell and this is private API. In other words: using BWToolKit in your App will result in MAS rejections. Since I decided to use BWToolKit in Ascension (a great enrichment), I created a variant without private API.

BWToolKit is one of the best known Cocoa frameworks / IBPlugins, for good reason. It contains commonly used UI elements and other objects designed to simplify your Mac development process. In short: create stunning interfaces on the fly. The image above explains very much of what BWToolKit is capable. You may want to have a look at the BWToolKit website for further details. The framework has been created and is maintained by @brandonwalkin, drop him a note and say "thank you" for his awesome creation. If you take a close look at the image above and compare it with the one on the website you will notice something is missing. It's the BWTokenField mentioned above. I took all BWTokenField related classes and resources from the project and the Interface Builder plugin. I recompiled it and it works like a charm. According to the reports seen here it's save to use with said modification. So if you love the Mac App Store and you love BWToolKit, this is your solution: a MAS save variant. You can download the compiled framework from here, IBPlugin is included, too. 

BWToolKit 1.2.5 without private API