You know you love what you're doing when you completely forget to drink your coffee...
styofa doing anything

Kiana Khansmith

祝日 / Permanent Vacation

JVL
dirt enthusiast
art blog(derogatory)

❣ Chile in a Photography ❣

Alisa U Zemlji Chuda
h


Discoholic 🪩
Aqua Utopia|海の底で記憶を紡ぐ
Three Goblin Art
todays bird
he wasn't even looking at me and he found me

Andulka
NASA
2025 on Tumblr: Trends That Defined the Year
Claire Keane
seen from United States

seen from Germany
seen from Malaysia
seen from United States

seen from United Kingdom
seen from Australia

seen from Canada

seen from Malaysia

seen from Malaysia

seen from Malaysia
seen from United States
seen from United States

seen from France
seen from Malaysia

seen from United States

seen from Germany

seen from South Korea

seen from T1
seen from United States
seen from Philippines
@amg1976
You know you love what you're doing when you completely forget to drink your coffee...

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
AVAudioSession and interruptions
In the project I’m currently working on, I want to set the audio session correctly because in BedtimeStoriesCollection sometimes the users complain about not having sound at all. Since one of the things that I’m NOT doing is set the audio session, maybe it can be the root of the problem.
Either way, since this new app is heavily based on sound, let’s do the things as it should. One of the events that I was having some issues dealing with was the interruption notification caused either by a phone call or a Calendar event. If the sounds were being played by an AVAudioPlayer instance there would be no question whatsoever because the framework is responsible for setting the session active after the interruption ends. But with Audio Units that’s not the case so you must explicitly set the session active again, after the end of interruption:
NSError *endInterruptionError = nil;
[[AVAudioSession sharedInstance] setActive:YES error:&endInterruptionError];
It's built on top of Qt, so it works on every major operating systems. It's a good companion for your CoreData sessions, whether you need to check your data or make some adhoc queries.
iOS, profiles, adhoc builds...
Such a frustrating day... Ended up without being able to install an adhoc build for a new app. I can't understand what's happening because I have made this lots of times: create app id, enable push notifications, create developer and distribution profile, update profiles on Xcode, set profiles on build configurations, archive, distribute, install, run and... CRASH!!! If I disable push notifications and re-generate the profiles, it works... What tha hell is going on?!?!
Apple’s sample Core Data templates suck.
I will soon find out as I'm about to start working on this part for my newest iOS project...
More in this post from Mike Nachbaur

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Maybe its an age problem, but now I can't go past 1am without making a big effort to keep mentally awake.
Exceptions (represented by NSException objects) are for programming errors, such as an array index that is out of bounds or an invalid method argument. User-level errors (represented byNSError objects) are for runtime errors, such as when a file cannot be found or a string in a certain encoding cannot be read. Conditions giving rise to exceptions are due to programming errors; you should deal with these errors before you ship a product. Runtime errors can always occur, and you should communicate these (via NSError objects) to the user in as much detail as is required.
from here
Sometimes we need to go back to the basics. If possible don't use @try/@catch, instead create a NSError instance and return it by reference, such as:
- (BOOL)doSomethingThatMayGenerateAnError:(NSError **)errorPtr;
First one!
Yeayy!