iDev: iOS Device not detect by xcode-5

Hi Friends,

Today I found a one major issue with XCode, Actually I upgarde my iOS Devices (6.0 to 7.1 ) , after that my device not detected by Xcode 5.0,with this error on organizer,

“The version of iOS on “iPhone/iPad ” is not supported by this installation of the iOS SDK. Please restore the device to a version of the OS listed below, or update to the latest version of the iOS SDK; which is available here.”


Please upgrade your XCode to 5.1 and above version using the OS X App Store application, your reference links are :

And fix this issue.

For Reference : Here

Thanks 🙂



iDev: Finding Your iPhone’s Unique Identifier (UDID)

Hi Friends

What is the UDID?

Each iPhone or iPod Touch has a Unique Device Identifier (UDID), which is a sequence of 40 letters and numbers that is specific to your device. It’s like a serial number but much harder to guess. It will look something like this: 2b6f0cc904d137be2e1730235f5664094b831186.

Why do we need the UDID?

Your iPhone can only install programs that are approved by Apple. Applications in the App Store have been approved by Apple for general distribution, but beta customers get to try the app before it’s in the store. We register your UDID with Apple so they can approve our application especially for your iPhone.

How do I get my UDID?

You can copy/paste your UDID from iTunes or email it directly from your device by using a free app from the App Store.

Email Using the Free App (iTune)

Install and run Ad Hoc Helper. It will create an email with your UDID. Send it to

Copy/Paste from iTunes

  1. Launch iTunes and connect your iPhone.
  2. In the right pane, locate the information about your iPhone, including its name, capacity, software version, serial number, and phone number. Plugged-in-iphone
  3. Reveal the Identifier by clicking on Serial Number:. Clicked-serial-number
  4. Copy the Identifier to your clipboard by choosing EditCopy. Edit-copy
  5. Paste the Identifier into an email to (You should be able to paste into your mail program or web browser by selecting EditPaste).

Reference : Here

Thanks , Keep Coding 🙂

iDev: iOS developers now can register up to 200 iOS devices for testing

As we all know the number of the products increasing for iOS, there is some good news for iOS developers. Apple has quietly increased the number of devices that can be registered to their developer account from 100 to 200.Apple_gray_logo

Since the launch of the App Store, Apple has allowed only 100 devices/UDIDs to be registered per developer license per year.


Although developers can remove devices from their account, they still get counted against their 100 device per year limit.

The 100 device limitation has been one of the biggest pain points for developers, especially since Apple has expanded its iOS product lineup to include the iPad and iPad mini. It is also extremely restrictive for companies that created number of apps per year.


Apple hasn’t updated its support documentation, so it is not official yet. but the before the rumored iphone lunch event updating this news defiantly helps the developers.

If you’re a developer we would love to know what you think of Apple’s decision to increase the UDID limit. Should Apple remove this restriction? or at least keep this cap at an app level?

Reference Link : Here

Thanks , Keep Coding 🙂

iDev Design : 5 Tips to design your mobile application

5 Tips to design your mobile application

If you want to make your mobile app succeed, you need to get a great user experience (UX). It is useless to have a good idea if you are not capable of showing it to your users.

While I was defining and structuring my last mobile app, I repeated and repeated what I consider the main goal: keep it simple.

Keep it simple via pinterest

1. Keep it simple

A mobile app should be simple and easy to use for someone who has never use it before, this is, user friendly. The most important features should be identified intuitively and quickly accessed. This is the starting point and despite being obvious, my experience shows that it is frequently forgotten. For example try to avoid creating deep navigation hierarchies.

This simplicity goal can be achieved by selecting an appropriate pattern to structure our application. This pattern depends on your specific needs.


2. Consider recommended patterns

Consider using the design patterns published in the mobile developer guides. Native applications and the operative system itself follow these patterns, so do a lot of other mobile applications. Users are used to navigating through different applications in a similar way. If your application behaves differently, users may get confused. As Android developer guide says, if it looks the same, it should act the same.

Check iOS user experience guidelines and Android design patterns.

3. Basic functionality

We tend to fill empty spaces and insert as much information and options as possible. We also tend to add a lot of features that are probably not useful to the users. These additional features delay the app publication date and what it is worse, they make our app more complex. When the definition is done in coordination with the clients or non-technical people, they will suggest more features: “Why don’t we add here this…?”, “Where can we include this function…?”, “I saw this other app that does…”, “Let’s develop some augmented reality functionality, it’s so cool…”.

I think that the best approach is to wait until the app is stable enough, and then start improving it by adding new features. This new features will come up as we use the app day by day.

4. Multiple screens

There are devices in a wide variety of screen sizes and form factors. Scale your app from large tablets to smaller phones, portrait or landscape mode, and focus your efforts on the most common screen sizes. Take a look at the Android dashboards.

devices options

5. Minimize the user effort

Help the user to use your application. Keep form data or the parameters configured in the last search, this will minimize the effort needed to use the app.

The most important data to be stored is the login data. Remember your user. But be careful not to hide all the content before the user logs in. It is a good idea to let the users navigate through much of your app without logging in. The login screen can be an obstacle to continue using your app.

Reference Source : Here

Thanks 🙂 Keep Coding 🙂


Keep Coding and Designing 🙂


iDev :Building for Devices (iPhone/iPad)

How to create a build:


This document will discuss the build process and the tools to create a build you can run on your phone, as well as the necessary steps to get an application on the iTunes App Store.

Most of the complexity lies in the Apple developer process for creating and installing signing certificates. This document guides you through that process from the beginning. If you already have your Apple certificates installed on your development machine, you can skip directly to Building your App using Corona.

Important note

Apple sometimes makes changes to these processes. For the latest and most accurate information, please refer to Apple’s documentation.

What you will need

In order to submit an application to the App store, you must have a version of XCode that is the same or newer than the version of the OS on your phone. For example, if you have version 3.0 of the iPhone OS installed, you will need XCode that is bundled with the iPhone SDK version 3.0 or later.



  • Developer account and Developer Certificate
  • Keychain certificate
  • Adding a Device
  • App IDs
  • Provisioning profiles
  • Building your App
  • Submitting your app to the app store

Developer account and Developer Certificate

Developer Account

To enroll in the iPhone Developer Program, go to the following Apple web site:

Click on the ‘Enroll Now’ button and follow Apple’s instructions on applying for a certificate. Currently there are two programs, ‘Standard’ and ‘Enterprise’. Choose the program that best fits your needs.

Keychain Certificate

Once you have signed up for the developer program, you will need to use the ‘Keychain Access’ tool located in your utilities folder in order to create a certificate request. This will be used to authenticate your computer.

Open Keychain Access and click on the Keychain Access menu bar item:

Select ‘Request Certificate from a Certificate Authority…’. This will bring up the following window:

Type in the email address you used for your apple developer certificate in the ‘user email address’ field. For Common Name, use the name of the Team Leader or yourself if you do not have a team. Click ‘Saved to disk’ and ‘Let me specify key pair information’. Upon clicking ‘Continue’, you will be asked to choose a save location. Pick a location that is easy to find, such as the desktop. You will then be prompted with the following:

Make sure that 2048 is selected for the Key Size and RSA for the Algorithm, then hit ‘Continue’. This will generate the key and save it to the location you specified. Click ‘Done’ in the next window. Now navigate to the following url:

Click on Certificates in the left hand column:

Now click on the ‘Add Certificate’ button.

Click on the ‘Choose File’ button and locate your certificate file that you saved earlier, and hit the submit button.

Once you hit submit, an email will be sent to the email address you specified in the Certificate Authority (CA) request form from Keychain Access. If you are the team leader, you will get this email and can approve the request yourself by hitting the approve button:

If you are waiting on approval, you will see the following screen:

You will see this until your request has been approved. Once it has been approved, you will be able to download the certificate:

Click on the download button and save the certificate to a location of your choosing.

Once this is done, double click on the file and you will see the following dialog:

Click ‘OK’. This will install your iPhone Development Certificate in your Keychain.

Adding Devices

This iPhone developer program allow you to have up to 100 devices per team. To register a device you will need the Uniques Device Identification (UDID) number. This can be found in two places, iTunes and XCode.


Normally when you plug in your device, and then open XCode, the ‘Organizer’ window will be open. If it is not, click on ‘Window’ and select ‘Organizer’:

Once the Organizer window is open, you should see the name of your device in the ‘Devices’ list on the left. Click on it and select the identifier with your mouse, copying it to the clipboard:

Note: if the colored indicator under the “Devices” list is yellow rather than green, turning the iPhone off and on again will usually re-synch it properly.


With your device connected, open itunes and click on your device in the device list:

Click on the Summary tab at the top:

Now click on the serial number to reveal the UDID:

Simply hit Command-C to copy it to the clipboard.

Adding/Registering the Device

To add a device to your Teams device list, click on ‘Devices’ in the iPhone Developer Program Portal and click on ‘Add Devices’.

Here you will be able to name your device as well as input the Device ID that you have stored in your clipboard. Once you have done this, click the submit button.

App IDs

In order to obtain provisioning profiles, you will first need to create an App ID. The App ID allows an application to communicate with the Push Notification service and/or any external hardware you have for your application. It can also be used to share keychain information, such as passwords, between a suite of applications. Regardless of whether or not you make use of such functionality, every application must have an App ID.

An App ID consists of a 10 character “Bundle Seed ID” prefix generated by Apple and a “Bundle Identifier” suffix that is created by the Team Admin in the Program Portal. An App ID could look like the following example: or To create a new App ID, click on the ‘New App ID’ button in the ‘App ID’ section of the program portal.

Fill in the ‘Description’ field with the name of your application. If you have already created an application and wish to use the Bundle Seed ID, for instance if you have a free version and a paid version of an application, you can select it in the ‘Bundle Seed ID (App ID Prefix) section on this page. If this is the first in the bundle or a standalone application, select ‘Generate New’. In the ‘Bundle Identifier (App ID Suffix)’ section, specify a unique identifier for your app. This can be just about anything you want for it to be, but it is recommended to use the reverse-domain style string, i.e. com.domainname.appname. For Corona Labs it might look like:


Note: it is often easiest to create a “wildcard” App ID that you can share between your various applications. To do this, simply create a single App ID with an asterisk (*) at the end. You would place this in the field for the bundle identifier either by itself or at the end of your string: com.domainname.* The general drawback of this method is that it cannot be used with any application employing Push Notification, since that requires a unique App ID for each application. However, since Corona does not yet support the Apple Push Notification Service, this restriction does not currently affect Corona development.

For more information on this topic, please visit the Apple Developer site.

Provisioning Profiles

There are three types of provisioning profiles for the iPhone program: Ad Hoc, Development, and Distribution. These profiles tie your devices to your development team for testing and distribution.

Note: The Ad Hoc and Distribution provisioning profiles are not available when running the trial version of Corona. If you are running the trial version, you should build with the Developer’s provisioning profile.

The Distribution Profile is what you use to build an application with the express purpose of putting it on the app store. It is not intended to be used for testing.

The Ad Hoc and Development Provisioning Profiles are used similarly, but you will only need to use the Ad Hoc profile with Corona. The Development profile can be used, but is not necessary.

Note: You do not need to add a CFBundleIdentifer field to the build.settings file when you are ready to submit your app to the app store. This is done automatically by Corona.

Ad Hoc Provisioning Profile

To obtain your Ad Hoc Provisioning profile to test on your device, you will need to create one in the iPhone Program Portal. From the Portal, click on the ‘Provisioning’ menu. From there click on the ‘Distribution’ tab:

Below this you will select the devices you wish to authorize for this profile. For most people, this will mean checking all of the devices available.

Now click the ‘Submit’ button.

You will now be returned to the Distribution tab where the status will most likely say ‘Pending’ . This process normally only takes a few seconds. Hitting the ‘Refresh’ button is normally enough time for it to be come active. Then you can ‘Download’ the profile. You will need to place it in the following directory:

/Users/(your user)/Library/MobileDevice/Provisioning Profiles/

If you do not have a ‘Provisioning Profiles’ folder, you will need to create it. Remember to substitute your username for (your user). For example:

/User/JohnGlenn/Library/MobileDevice/Provisioning Profiles/

Distribution Provisioning Profile

In order to submit your app to the app store, you will need to download the Distribution Provisioning Profile. This process is very similar to obtaining the Ad Hoc profile. Click on the Distribution tab in the Provisioning section of the Program Portal:

Instead of selecting ‘Ad Hoc’, this time we’re going to use ‘App Store’ for the distribution method.

Give your profile a name, such as “TestApp_distribution” and click on the ‘Submit’ button. You will be brought back to the Distribution Provisioning Profiles list, where you should see your profile listed and marked as ‘Pending’ in the Status column. Refresh the page and you should be able to download your profile into the same folder that you used for your Ad Hoc profile.

Building your App using Corona

Building your application using Corona is a simple process once you have your provisioning profiles in place. You must also make sure that you have a connection to the internet. You can build your application for testing in the XCode Simulator, or for testing on a device.

To build your application, open the Corona Simulator and open a project (select File > Open … to open your project, or choose one from the Corona welcome window). Then select File > Build > IOS … The following dialog appears:

Fill in the application name and version number fields with the relevant information, and select the target device (iPhone or iPad) from the Device Compatibility drop-down menu. To test the compiled application in the XCode Simulator select XCode Simulator from the Build For drop-down menu, or Device to build an app bundle for testing on a device. Lastly, select the appropriate provisioning profile from the ‘Code Signing Identity’ drop-down menu, either adhoc or distribution.

Note: if you have not loaded these profiles into the standard location on your hard drive, you will have no options in this drop down menu. Provisioning profiles should be placed in the following directory as mentioned in previous sections of this document:

/Users/(your user)/Library/MobileDevice/Provisioning Profiles/

Once you have entered all the relevant information, you may hit ‘Build’. Once Corona has completed the build, it will output an application to the ‘Save to folder’ you have chosen. By default this location is set to the desktop, and you will see an option to ‘Show in Finder’.

Congratulations! You now have an application file that can be placed on your device, or submitted to the App Store, depending on which provisioning profile you selected.


Application Icon

The application icon for iPhone should be a 57 x 57 PNG image file (or 72 x 72 for iPad). It should have the nameIcon.png and be located in the assets project folder. For iPhone / iPod touch apps, an additional high-resolution 114 x 114 icon named Icon@2x.png is now also required to support Retina displays.

        Icon.png        <--- required for iPhone/iPod/iPad
        Icon@2x.png     <--- required for iPhone/iPod
        Icon-72.png     <--- required for iPad

Add the following to your build.settings file:

settings = 
    iphone =
        plist =
             CFBundleIconFile = "Icon.png",
             CFBundleIconFiles = {
                    "Icon.png" , 
                    "Icon@2x.png" , 
                    "Icon-72.png" , 

Note: the App Store requires a 512 x 512 pixel version of the icon, so you should always create the icon in this higher-resolution. Please refer to the Apple iOS Human Interface Guidelines for the latest official App Store requirements.

Using a pre-rendered icon (no gloss)

To keep iOS from rendering your icon with the default gloss across its top, add the following plist setting to your project’s build.settings file:

settings = 
        iphone = {
                plist = {
                        UIPrerenderedIcon = true,

For more information about build.settings, see Build Configuration.

Launch Image

When your application launches, you can choose to display a launch image before your application finishes initializing and is ready to display its interface. By using an image that looks like the initial user interface, you can create the illusion of a faster application launch. Alternatively, you can use this image for a “splash screen” displaying your application title or company logo.

The launch image for iPhone should be named Default.png and be the dimensions of the screen. It should be located in the assets project folder.

        Default.png     <---

For the iPad, Apple encourages the use of launch images for all orientations supported by your application, and the App Store reviews may reject applications that don’t conform to this rule. The iPad uses the following naming conventions for orientation-specific splash screen files:


See the “Orientation Support” section in the Corona API Reference for more information about using different orientations in your app.

Testing your App on your iPhone or iPad

To run the application on your iPhone or iPad, select the adhoc profile during the build process, as detailed above. You may then use either iTunes, XCode, or the iPhone Configuration Utility to transfer the application file.

To use iTunes, drag the application into your iTunes Library and then synch your device normally.

However, it is considerably faster to use either the iPhone Configuration Utility or the XCode Organizer. Also, these methods allow you to test on devices that are not synchronized to your iTunes account.

The iPhone Configuration Utility is available as a separate download from the iPhone Dev Center ( In the “Downloads” area near the bottom of the page, you’ll find it in the “Other Downloads” section:

With your iPhone connected to your computer, launch the iPhone Configuration Utility and then click the “Add” button at the top left:

The final step is to click on your device name under the “Devices” section on the left; this will show a list of all currently installed (or added but not yet installed) iPhone apps. Click the “Install” button next to the app you added to the utility:

Finally, XCode provides a convenient method for installing iPhone applications. With the phone connected, open XCode’s Organizer window (Window > Organizer), and look for the name of your device under the ‘Devices’ list on the left. Make sure that the colored indicator is green; if it is not green, powering the iPhone off and on again will usually establish a proper connection.

At this point, you can simply drag the newly built application file and drop it in the ‘Applications’ area at the bottom of the window, and it will automatically install on the iPhone.

Note: if you are repeatedly testing versions of the same application, it is usually a good idea to delete the previous version from the iPhone before each new install, to remove any cached or associated data.

Submitting your App to the App Store

Once you have built and tested your Application with Corona, it’s time to submit it to the App Store. To do this, you will need to access “iTunes Connect” from the iPhone Dev Center. If you are currently browsing the ‘iPhone Developer Program Portal’, you will need to exit the portal and return to the ‘iPhone Dev Center’.

Once you are back in the ‘iPhone Dev Center’, you will need to click on ‘iTunes Connect’ in the right hand column.

If you are planning on releasing your application for free, you can skip ahead.

If you are planning on charging for your application, you will need to agree to Apple’s contracts. To do this, click on the ‘Contracts, Tax, & Banking Information’ link.

When you have read and agreed to the Paid Applications contract, you will need to fill out the necessary banking, contact and tax information. Once you have completed this, you will be able to submit your application for sale.

Now go back to the iTunes Connect screen by hitting the ‘Done’ button.

Once you are there, click on the ‘Manage Your Applications’ button.

From this point you will begin Apple’s ‘Add New Application’ process. Answer the questions appropriately. When you get to the upload section, you will need the following items:

  • The application, zipped in an archive.
  • A large icon in PNG format, very similar to the normal 57×57 icon, but 512×512 pixels in size.
  • At least one screenshot of the application to serve as the primary screenshot
  • Any additional screenshots that you may have (up to 4 more)

Note: you should add your application’s icon during the Corona build process by placing the icon file (named ‘Icon.png’ with dimensions of 57 x 57 pixels) in the same directory as all your other code and image assets. The rounded corners and ‘shiny icon’ effect will be added automatically. You can also add an application splash screen by placing a file named ‘Default.png’ (320 x 480 pixels) with your other assets before building.

When you go to upload files, be sure to click the upload button for each, and wait for it to complete before moving on to the next upload. When you have completed this, click ‘Continue’.

The pricing screen will allow you to select the availability of your app as well as the pricing tier. If you have agreed to the contract and filled out the necessary paperwork, you may still get a warning if the paperwork has not gone through yet. That particular process may take several weeks. You will still be able to continue, but your application will not become available until after your contract information has been processed and your application reviewed. You can also specify which worldwide stores you want to make your application available in.

Once you are finished with this stage, hit the ‘Continue’ button to select any additional languages you wish to support.

Hit ‘Continue’ when you have completed this.

You should now see the Review screen. Check over this to make sure everything is in order before submitting your application. If everything is in order, hit the Submit button.

Now your application should be added to the review process! This can take time, so be patient: as of this writing, approvals are often taking around two weeks, but longer delays are definitely not unheard of. Apple has strict guidelines on what they will allow into the app store, so don’t be surprised if you have to make changes to get your application published. If you don’t feel that you have received enough guidance regarding the changes they want, you can try writing back to ask for further detail.

To learn more about Apple’s design philosophy for mobile applications, consult their Mobile Human Interface Guidelines on the Apple developer portal:

Reference URL : Here

Thanks 🙂 Keep Coding 🙂


iDev: Build and Run an xcode project via terminal (Command Line Tool)

Hello Friends,

Today I post a very simple but important technique to build the application using terminal.

How to build and create .app file from out side Xcode i.e. with/using terminal.

Procedure  :

1-> Open Terminal (Go to Spotlight and search terminal)

2-> Go to specified project folder using cd command , Suppose you create a iPhone application project , project named : SampleApp , which is located in your Desktop.

So you can write in the terminal like this :

MacMini: Admin$ cd Desktop\SampleApp

3-> After than you can write this command on the terminal

xcodebuild -target ‘AppName.xcodeproj’ -scheme ‘AppName’ -configuration “Debug/Release” -sdk iphoneos6.0/5.0/4.0 -arch “armv7 armv7s” CONFIGURATION_BUILD_DIR=’BuildDirectoryName‘ ONLY_ACTIVE_ARCH=NO/YES

For our SampleApp example you can write on the terminal as:

MacMini:SampleApp Admin$ xcodebuild -target ‘SampleApp.xcodeproj’ -scheme ‘SampleApp‘ -configuration “Debug” -sdk iphoneos6.0 -arch “armv7 armv7s” CONFIGURATION_BUILD_DIR=’TestBuild‘ ONLY_ACTIVE_ARCH=NO

4-> After that your build folder is created and .app file will be there in TestBuild Folder. Path : Desktop/SampleApp/TestBuild/

For Further references you can read here:

Thanks 🙂 Keep Coding 🙂



WWDC 2013: iOS 7 and Mavericks’ missing features

By  for The Apple Core | June 12, 2013

Summary: While the developer previews of iOS 7 and OS X Mavericks showed some evolutionary new features, there are several new features that are still lacking in Apple’s new operating systems.

WWDC 2013: Features missing in iOS 7 and Mavericks - Jason O'Grady

The developer previews of Apple’s iOS 7 and OS X Mavericks that were announced yesterday at WWDC are packed with new features — and an entirely new user experience in the case of iOS 7 — but I was disappointed that several needed features didn’t appear to make the cut.

There are a number of features that are noticeably absent from the first developer build of iOS 7 (11A4372q). These should be taken with a grain of salt however, as a lot can change (and hopefully will!) before iOS 7 is released in the fall.

Default apps – There’s no way to change default apps, so we’re stuck with Safari, Email and Calendar, for the time being.

Lower case keyboard – Although there are some nice UI tweaks to the new keyboard, lower-case keys are still represented by capital letters. Something I’ll never understand.

Alternative keyboards – I’m not holding my breath for this one. Apple’s previously said that third party keyboards are a security risk because they can contain key loggers.

Landscape springboard – I still find it amazing that the iPad home screen can be displayed in landscape mode, but the iPhone’s can’t. Curiously the new iOS 7 Multitasking Switcher and Control Center both work in landscape (as do most apps, including Mail, Messages and Safari) yet the springboard doesn’t.

Upside-down springboard – When Jony Ive finally realizes that landscape mode is useful on an iPhone, I hope he allows the Springboard (and apps) to be used fully upside-down too (like the iPad does). Since the iPhone 5’s ports on the bottom of device, it’s almost impossible to use when plugged into power and sitting upside-down in the cup holder of a car.

Public transit directions – The updated Apple Maps app while improved, still refers you to other apps and the App Store when you touch the link for “transit directions”

Widgets – Although we got similar functionality in Control Center and Notification Center, there’s no substitution for real, live widgets. But Jony Ivy continues to tease us with his animated iOS icons! First it was the updating date on the Calendar app, now the Clock icon is live, right down to the sweeping second hand.

Lock screen widgets – While the new Today screen in Notification Center is an improvement over iOS 6, I’d still prefer to have real widget that I can customize.

Menubarlets – Apple tweaked the menu bar in iOS 7 with carrier dots and a new charging icon, but there’s still no way to add icons for things like the current temperature, like you can in Android.

Multiple user accounts – While Apple hasn’t released a version of iOS 7 for the iPad yet, there’s no signs of multiple user support in the current developer build of iO7, so it’s looking unlikely this go around.

Better/more printing options – While the new Share Sheet and AirDrop functionality are welcome additions, they don’t change the fact that there are only a small amount of printers that support AirPrint.

OS X Mavericks is missing one major feature that was rumored to be coming: full Siri integration. The first developer build of Mavericks ships with the same Dictation and Speech Control Panel that debuted in Mountain Lion (OS X 10.8), but no Siri. Which is a shame. Hopefully Siri will arrive in a subsequent build of Mavericks.

I’m sure more missing features will come to mind, and I’ll update this post when then do. In the mean time, what’s missing in iOS 7 and Mavericks for you?

Source : Click Here