#quickcal

We recently released version 1.6 of QuickCal for the iPhone. 

There is not much in our latest updates you might notice right away. But there are some huge improvements under the hood which I want to point out to you. 

The biggest improvement is the new engine, which now works even better than our Mac version. This should be noticeable not only when you type stuff but also while using dictation. (Which works perfectly! Try it out!)

We also added a feature to the iOS version that makes creating events for a specific day even faster. If you tap and hold on a given day in both list and month view this will set the date for you and you just have to add the missing pieces (title, time, location). 

We also improved the birthday calendar integration … not only visually but also functionally. Just like in Apples calendar you are presented with contact details when tapping on a person. This way you can easily call that person, write an email or post something on the person's Facebook wall. 

And that still isn't all. You now can launch the app directly to the entry view (if you like even with an app like Launch Center Pro). Switching between views should be a lot faster. iPhone 5 / iOS 6 support…

We don't get a lot of press but I hope you - our users - appreciate the improvements. If you do, please tell your friends about QuickCal and help us by leaving a positive review in the Appstore.

First time using Xcode 4 to submit my Mac App to the store today ... Did a lot of work to make it play nice w/ Mountain Lion, App Sandbox, Developer ID, ...

1) Build and Archive - and realize I don't have an App Bundle created, but a generic Xcode archive. You can't submit those to the store.

2) Found this great article on stack overflow about how child/dependent projects need to have "Skip install" set to yes in their application build settings for the project to be created as a normal Mac App Bundle. I change it, compile my project, and errors everywhere (which seem like stuff I'd see if my provisioning profiles were zapped, or info.plists removed...)

3) Freaking out a bit, I go to my projects build summary page, and am surprised to see the icon for my MAS target is not set anymore, I'm missing my app category, the bundle ID is different (?), build isn't a build number anymore but a "1.0".. I fear my project was just destroyed.

4) Time Machine to the rescue! I move my entire project to the trash, pull up time machine, find a version from early this morning, and restore... Tick, tock... ERROR. "The operation can't be completed because you don't have permission to access 'name-of-config-file-in-my-project'". Huh? Does that mean I can't write to the directory? Read from my backup disk?

5) I manually copy the directory from my backup disk to my Desktop (which works), and then make a copy of that and put it in my projects directory... Fire up Xcode, and get a ton of errors about how my project is locked - do I want to unlock? I click 'yes', and then get errors saying my "project.pbxproj" file is locked.. Xcode won't even close for me; I'm forced to force-quit it at this point.

6) After repeating step 5 a few times, I find this awesome post which clued me in about ACLs (most importantly, how to identify they were at play and how to get rid of them). Did that, and bam - I can now get access to my project again.

7) Back in Xcode. Verify all the settings on my target summary page look fine, go to build settings of my subproject, set "Skip Install" to YES, build+archive.. Sucess, but huh? My archive is missing an icon, and it fails validation. (Because category wasn't set, my bundle id didn't match the store's idea of what it was, ... essentially describing the issue in #3). I go back and look at settings, and they're gone again!

8) Closed Xcode, deleted my project dir, pulled over the copy off my desktop, repeated step 7 a few more times. Failed just the same.

8.5) Checked the Mac App Store - surely there's an update to Xcode. Nope. I'm on the latest.

9) Repeated step 8, ... but this time, I took screen captures of the "before", and just re-set everything up again. Build and archive, success... Archive file looks good.. Verifies... DONE!

WTF is this about? I sure hope Apple didn't just make the playing field even more uneven... While submitting this app to the Mac App Store tonight, it seems what I've done in the past is now wrong.

From TFAD:

On this episode of KP, we're joined by Mark Jardine of Tapbots. We talk Tapbots, Tweetbot, and adventure games starring robots!

Topics

Tweetbot released!

Picks

Verbs

League of Evil

You Don't Know Jack

Quickshot

QuickCal

QuickCal Mobile