![]() I also have an additional 10 words or so that I’ve been tracking. I believe it’s a tad over 100 characters. The title of my app? You ready? Tomorrow: Record Inspiring and Influential Messages Today with Your Voice, Get it Tomorrow to Inspire Your Future Self So in case you didn’t know, while it’s not completely clear, it appears that App Store Optimization (ASO) is based on 100 characters of keywords that I provide along with what’s in my title for the app. I’ve been using Sensor Tower for the past 2 weeks and it’s been absolutely amazing in helping me track my app keywords. I love working on POSTs and GETS to and from the backend!īruce Lee states: “I don’t fear the man that knows 10,000 kicks, I fear the man that practiced one kick 10,000 times.” Setting up UI stuff whether it’s programmatically or via storyboard, I absolutely love. I want to continue to master the things that I’m good at and round out my weaknesses. It’s crazy that just a year ago, I was looking at the objective-C books and thinking how the hell am I going to learn this crap!? As I continue to read through Swift books, I’m finding new ways to refactor my code and make it more Swifty. I enjoyed the very uniform and verbose way of writing objective-C because I think it taught me a disciplined way of writing code. I do struggle daily with writing code in a more swifty way, but it’s a good thing. I’m very much glad I learned objective-C first still. Should I learn Swift? Should I learn objective-C? The mentality it seemed was that if I wanted a job, learn obj-C, if I want to build apps, learn Swift. I remember when I began learning the iOS framework Swift had just been announced and it was the age old debate. It’s a small team, but we move really quickly and it’s so much fun to tackle new challenges. We’re making apps for the interior design space by helping individuals find products for the world’s interiors and creating a solutions to help designers manage client relations more efficiently. Check them out!) The three above really allowed me to pause and think about multiple layers of the vast world of iOS.Īdditionally, I’ve had the pleasure of working at Musey for the past few months. I’m positive there are quite a few more that are amazingly impactful and informative unfortunately, I didn’t have the time to see them. Matt Ronge - Lessons in App PR: How to LaunchĪbezir Nazir - What Haskell Teaches Me About Swift I was fortunate enough to attend AltConf. Seems silly because we live in a digital world where we receive the latest news and texts on our very watches, but still, it’s a must. Note to self: Make business cards just for this event. I was in the thick of it experiencing WWDC afterparties, getting to know quite a few smart developers. So much has happened over the past few months. I was fortunate enough to get a job very shortly after my last post which is what has caused this extended absence. i use only because it was the first i tried, it was pretty easy for me to manage and pretty painless for my beta testers.It’s been months since I’ve updated this little thing and I hope this doesn’t become a habit. could this work for some reason on your devices but not on the failing devices? if so, you could be asking to record in a top level directory when you did not mean to.Ĭan you get the testers you have onto a "beta" list? sign up for something like TestFlight or Hockey Kit, get one or more of the users with a failure to record to also sign up, and then upload a beta of your app with diagnostics that put a dialog on screen with the resultant "error". this could cause the filename to be simply ".caf". have you tested by playing with the verseGUID, bRecordReference values? maybe your devices never have a bad verseGUID, but the devices on which no recording happens have a nil/empty verseGUID. The url passed to initWithURL could be malformed: The real question you want answered seems to be: what would cause the recording not to occur?ĪudioRecorder could be nil or audioRecorder prepareToPlay could be returning NO. ![]() It could be many things not having to do with the recording settings. Int errorCode = CFSwapInt32HostToBig()",, (char*)&errorCode) ![]() NSString *fileName = documentsDirectoryPath], fileName]] ĪudioRecorder = initWithURL:url settings:recordSettings error:&error] NSDictionary *recordSettings = [NSDictionary dictionaryWithObjectsAndKeys: Are any of my settings off? App requires iOS5 and uses ARC. I've had trouble finding sample settings for AAC format. This isn't happening on our test devices, but the reports show that the problem is that prepareToRecord is returning NO. I've got a live app with an estimated 15% of users reporting that the record feature is not working. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |