Amit : iphone Developer

1. Add the UIRequiresFullScreen key to your Xcode project’s Info.plist file and apply the Boolean value YES 2. This will fix one more issue that is coming at the time of iTune upload Invalid Bundle. iPad Multitasking support requires these orientations: 'UIInterfaceOrientationPortrait,UIInterfaceOrientationPortraitUpsideDown,UIInterfaceOrientationLandscapeLeft,UIInterfaceOrientationLandscapeRight'. If your application only using single orientation then use the above keyword in info.plist

iOS 8  : ~/Library/Developer/CoreSimulator/Devices/[Device ID]/data/Applications/[appGUID]/Documents/ Use below command to check you Device ID: xcrun instruments -s

Use  identifierForVendor,  this unique string is same till you not delete your application from the device. Swift :    var uniqueId = UIDevice . currentDevice (). identifierForVendor . UUIDString   println ( "identifierForVendor : \ (uniqueId)" )          Objective-C :  NSString * uniqueId  = [[[UIDevice currentDevice] identifierForVendor] UUIDString]; Refrence Link :  http://possiblemobile.com/2013/04/unique-identifiers/

Place Search API : Authentication :   https://developers.google.com/places/documentation/ Below detail coming from above link Need to first register for the API key then you are able to use below link services: The Google Places API uses an API key to identify your application. API keys are managed through the  Google APIs Console . You'll need your own server API key  before you can begin using the API. To activate the Places API and create your key: Visit the  Google APIs Console  and log in with your Google account. A default project called  API Project  is created for you when you first log in to the APIs Console. You can use the project, or create a new one by clicking the  API Project  button at the top of the window and selecting  Create .  Google Maps API for Work  customers must use the API project created for them as part of their  Google Places API for Work  purchase. Click the  Serv...

Create category that works for both iOS7 and iOS8 or only use sizeWithAttributes. #import "NSString+StringSizeWithFont.h" @implementation NSString (StringSizeWithFont) - ( CGSize ) sizeWithMyFont:( UIFont *)fontToUse {     if ([ self respondsToSelector : @selector (sizeWithAttributes:)])     {         NSDictionary * attribs = @{ NSFontAttributeName :fontToUse } ;         return ([ self sizeWithAttributes :attribs]);     }     return ([ self sizeWithFont :fontToUse]); } @end Category call :      NSString *text= @"Do any additional setup after loading the view, typically from a nib." ;     CGSize fontSize = [text sizeWithMyFont :[ UIFont fontWithName : @"Helvetica"                                             ...

Call below function like : [self toStringFromDateTime:[NSDate date]]; - (NSString*)toStringFromDateTime:(NSDate*)datetime {     // Purpose: Return a string of the specified date-time in UTC (Zulu) time zone in ISO 8601 format.     // Example: 2013-10-25T06:59:43.431Z     NSDateFormatter* dateFormatter = [[NSDateFormatter alloc] init];     //ISO DateFormatter     [dateFormatter setTimeZone:[NSTimeZone timeZoneWithAbbreviation:@" UTC "]];     [dateFormatter setDateFormat:@" yyyy-MM-dd'T'HH:mm:SS.SSS'Z' "];     NSString* dateTimeInIsoFormatForZuluTimeZone = [dateFormatter stringFromDate:datetime];     return dateTimeInIsoFormatForZuluTimeZone; }

Why migration required ? When the model does not match the store, a migration is required. In order to perform a migration, Core Data (technically, an instance of NSMigrationManager) requires these things: The destination managed object model (the one with the changes) A managed object model that can open the existing store The ability to infer mapping between the two models (for a lightweight migration), or a manual mapping model Permission to attempt to perform an automatic migration (for a lightweight migration) It is therefore absolutely essential that you never make changes to the managed object model for a released version of an app. That is, if your app is already in the App Store,  don’t change a single thing in that version of the managed object model . Solution for the Crash while update an application from the app store: Create a  new version  of the managed object model! This reminds me to mention some other best practices to adopt when worki...