A few things missing from iOS 7:

The ten thing that are no more available in iOS 7.0.

1) UIDevice uniqueIdentifier is probably the most notable of all these. It was deprecated back in iOS 5 but as of iOS 7, it is just flat out gone. Xcode won’t even compile if you try to call it. However, if any existing app on the device does call it, the returned value will no longer be the UDID but instead NSUUID.

2) MAC Address. This one goes hand in hand with the uniqueIdentifier. Apple really doesn’t want you getting at any kind of ID that will uniquely identify a device. If you try to get the MAC Address on iOS 7 you will only get back 02:00:00:00:00:00.

3) libsyscall gethostuuid .This one is part of Core Bluetooth. Apple is being very loud and clear: if you want any kind of unique ID use identifierForVendor, advertisingIdentifier, or CFUUID.

4) UIViewController wantsFullScreenLayout In iOS 7, all view controllers are full screen.

5) UIColor scrollViewTexturedBackgroundColor and the like are now deprecated. UIColor objects that provided background textures for earlier versions of iOS are gone.

6) MapKit has deprecated the entire MKOverlayView class in favor of the new MKOverlayRenderer now available in iOS 7.The existing overlay views have been replaced with an updated set of overlay renderer objects that descend from the MKOverlayRenderer class.

7) CoreLocation has deprecated CLRegion in favor of CLCircularRegion. The CLRegion class continues to exist as an abstract base class that supports both geographic and beacon regions.

8) The Audio Session API in the Audio Toolbox framework is deprecated. Apps should use the AVAudioSession class in the AV Foundation framework instead.

9) The UUID property of the CBCentral class is deprecated. To specify the unique ID of your central objects, use the identifier property instead.

10) Many drawing additions to the NSString class are deprecated in favor of newer variants.

1) Control Center (Some things should be only a swipe away. And now they are.)
2) Notification Center (Today is all about you.)
3) Multitasking (While you multitask, it dose, too.)
4) Camera (All the right formats. Right at your fingertips.)
5) Photos (Life is full of special moments. So is your photo library.)
6) AirDrop (Drop everything.)
7) Safari (With things out of the way, there’s way more web.)
8) iTunes Radio (Hear where your music takes you.)
9) Siri (You’re going to like what you hear. And see.)
10) App Store (Find the right app for wherever you are.)
11) Find My iPhone (And if you can’t, at least there’s this.)
12) iOS in the Car (Best passenger ever.)
13) Mail
14) Weather
15) Messages

Property Attributes Indicate Data Accessibility and Storage Considerations
Use Accessor Methods to Get or Set Property Values
01. atomic //default
02. nonatomic
03. strong=retain //default
04. weak= unsafe_unretained
05. retain
06. assign //default
07. unsafe_unretained
08. copy
09. readonly
10. readwrite         //default
01. atomic 
-Atomic means only one thread access the variable(static type).
-Atomic is thread safe.
-but it is slow in performance
-atomic is default behavior
-Atomic accessors in a non garbage collected environment (i.e. when using retain/release/autorelease) will use a lock to
ensure that another thread doesn’t interfere with the correct setting/getting of the value.
-it is not actually a keyword.
Example :
@property (retain) NSString *name;
@synthesize name;
02. nonatomic
-Nonatomic means multiple thread access the variable(dynamic type).
-Nonatomic is thread unsafe.
-but it is fast in performance
-Nonatomic is NOT default behavior,we need to add nonatomic keyword in property attribute.
-it may result in unexpected behavior, when two different process (threads) access the same variable at the same time.
@property (nonatomic, retain) NSString *name;
@synthesize name;
Suppose there is an atomic string property called “name”, and if you call [self setName:@"A"] from thread A,
call [self setName:@"B"] from thread B, and call [self name] from thread C, then all operation on different thread will be performed serially which means if one thread is executing setter or getter, then other threads will wait. This makes property “name” read/write safe but if another thread D calls [name release] simultaneously then this operation might produce a crash because there is no setter/getter call involved here. Which means an object is read/write safe (ATOMIC) but not thread safe as another threads can simultaneously send any type of messages to the object. Developer should ensure thread safety for such objects.
If the property “name” was nonatomic, then all threads in above example – A,B, C and D will execute simultaneously producing any unpredictable result. In case of atomic, Either one of A, B or C will execute first but D can still execute in parallel.
03. strong (iOS4 = retain )
-it says “keep this in the heap until I don’t point to it anymore”
-in other words ” I’am the owner, you cannot dealloc this before aim fine with that same as retain”
-You use strong only if you need to retain the object.
-By default all instance variables and local variables are strong pointers.
-We generally use strong for UIViewControllers (UI item’s parents)
-strong is used with ARC and it basically helps you , by not having to worry about the retain count of an object. ARC automatically releases it for you  when you are done with it.Using the keyword strong means that you own the object.
@property (strong, nonatomic) ViewController *viewController;
@synthesize viewController;
04. weak (iOS4 = unsafe_unretained )
-it says “keep this as long as someone else points to it strongly”
-the same thing as assign, no retain or release
-A “weak” reference is a reference that you do not retain.
-We generally use weak for IBOutlets (UIViewController’s Childs).This works because the child object only
needs to exist as long as the parent object does.
-a weak reference is a reference that does not protect the referenced object from collection by a garbage collector.
-Weak is essentially assign, a unretained property. Except the when the object is deallocated the weak pointer is automatically set to nil
Example :
@property (weak, nonatomic) IBOutlet UIButton *myButton;
@synthesize myButton;
Imagine our object is a dog, and that the dog wants to run away (be deallocated).
Strong pointers are like a leash on the dog. As long as you have the leash attached to the dog, the dog will not run away. If five people attach their leash to one dog, (five strong pointers to one object), then the dog will not run away until all five leashes are detached.
Weak pointers, on the other hand, are like little kids pointing at the dog and saying “Look! A dog!” As long as the dog is still on the leash, the little kids can still see the dog, and they’ll still point to it. As soon as all the leashes are detached, though, the dog runs away no matter how many little kids are pointing to it.
As soon as the last strong pointer (leash) no longer points to an object, the object will be deallocated, and all weak pointers will be zeroed out.
When we use weak?
The only time you would want to use weak, is if you wanted to avoid retain cycles
(e.g. the parent retains the child and the child retains the parent so neither is ever released).
05. retain = strong
-it is retained, old value is released and it is assigned
-retain specifies the new value should be sent -retain on assignment and the old value sent -release
-retain is the same as strong.
-apple says if you write retain it will auto converted/work like strong only.
-methods like “alloc” include an implicit “retain”
@property (nonatomic, retain) NSString *name;
@synthesize name;
06. assign 
-assign is the default and simply performs a variable assignment
-assign is a property attribute that tells the compiler how to synthesize the property’s setter implementation
-I would use assign for C primitive properties and weak for weak references to Objective-C objects.
@property (nonatomic, assign) NSString *address;
@synthesize address;
07. unsafe_unretained
-unsafe_unretained is an ownership qualifier that tells ARC how to insert retain/release calls
-unsafe_unretained is the ARC version of assign.
@property (nonatomic, unsafe_unretained) NSString *nickName;
@synthesize nickName;
08. copy
-copy is required when the object is mutable.
-copy specifies the new value should be sent -copy on assignment and the old value sent -release.
-copy is  like retain returns an object which you must explicitly release (e.g., in dealloc) in non-garbage collected environments.
-if you use copy then you still need to release that in dealloc.
-Use this if you need the value of the object as it is at this moment, and you don’t want that value to reflect any changes made by other
owners of the object. You will need to release the object when you are finished with it because you are retaining the copy.
@property (nonatomic, copy) NSArray *myArray;
@synthesize myArray;
09. readonly
-declaring your property as readonly you tell compiler to not generate setter method automatically.
-Indicates that the property is read-only.
-If you specify readonly, only a getter method is required in the @implementation block. If you use the @synthesize directive in
the @implementation block, only the getter method is synthesized. Moreover, if you attempt to assign a value using the dot syntax,
you get a compiler error.
@property (nonatomic, readonly) NSString *name;
@synthesize name;
10. readwrite 
-setter and getter generated.
-Indicates that the property should be treated as read/write.
-This attribute is the default.
-Both a getter and setter method are required in the @implementation block. If you use the @synthesize directive in the implementation
block, the getter and setter methods are synthesized.
@property (nonatomic, readwrite) NSString *name;
@synthesize name;

iPhone 4 iOS 5 not receiving MMS all the time:

1)Go To Settings>General>Network>Cellular Data Network
and put this settings

My MMS Settings are:
APN: wap.voicestream.com
MMS Proxy:
MMS Max Message Size: 1048576


APN: wap.cingular
MMSC: mmsc.cingular.com
MMS Proxy:
MMS Max Message Size: 614400

Now in Settings>Messages you can get MMS Messaging ON over here.


Localization is the process of translating and adapting both the content (text and style) and the presentation (graphical and technical components) of an EXISTING product according to the language and cultural characteristics of the target audience or region for which it is intended.

Localization and Internationalization are complimentary activities, with one we can display cultural information like units, dates in the user’s preferred locale and the other, let’s us display text in the user’s preferred language.

The first step is to find out what languages your application is going to support and gather all the text (in different languages), images, videos, sounds and put them in a resource file or in a language directory. To translate text into different languages you can a tool that Google provides here http://translate.google.com/#en|es|

Preparing for Internationalization

In our sample app, we are going to support three languages English, Hindi and Gujarati. Create a new project in Xcode, does not matter what template you select.

After you have created your project, open the project location in Finder and create three directories called en.lproj,gu.lproj and hi.lproj. These three directories become the language project for your application. All the English language resources will stored in the folder en.lproj, the Gujarati language resources will be stored in gu.lproj, and the Hindi language resources will be stored in hi.lproj folder. The resource files that contain the localizable string are called “strings” file and their default name is “Localizable.strings”. So, we will create two new strings file in Xcode, select Resources and click on File -> New File -> Other (under Mac OS X) -> Strings file and click on Next, name your file “Localizable.strings” and save it in en.lproj directory. Repeat the same process by saving it in gu.lproj directory and hi.lproj directory. This is how the files look like in Xcode, since Xcode is smart enough to figure out that the file is localized for three different languages.

For image cropping with UIBezierPath first you need to decide on close path so you put code for free draw. and using that all point you make one UIBezierPath. using that BezierPath we crop image and then we need to resize that image. and finally we get original cropped image. and then we clear image other part by set that cropped image as main image.

Image cropping contains three functionality
1. Free hand image selection for cropping.
2. Crop image according to selection.
3. Clear image cropping.

1) Siri
2) Facebook integration
–> Public API for developers
3) Phone
–> Reply to incoming calls with message (preset or custom) or save reminder (timed)
4) Center
–> Do not disturb toggle with fine-grain phone call exceptions, schedules, or allowing repeat calls
5) FaceTime
–> Apple ID unified with phone number, enabling FaceTime or iMessage answering on iPad or Mac
6) Safari
–> iCloud Tabs for Safari on other iOS devices and Macs, Offline Reading List, Photo uploads, Smart app banners link to App Store or launches, Fullscreen video in landscape
7) Photo Streams
–> Shared Photo Streams with designated friends, includes comments
8) Mail
–> VIPs – designated contacts cause notifications, e-mails flagged with stars, separate inbox,
Flagged mailbox
9) Passbook
–> Barcode collection for boarding passes, store cards, coupon, movie tickets
10) Maps
–> Local search with 100 million business listings with Yelp reviews and pictures, Crowd-sourced traffic data with incident reports, Free turn-by-turn navigation with alternative route offers based on faster ETA, Navigation viewable from lock screen, Flyover (3D buildings)
11) Accessibility
–> iOS 6 comes with Guided Access.
12) Camera with Panoroma
–> Broaden your horizons.


Get every new post delivered to your Inbox.