I would like to send my iPad app to testers who have xcode on their macs but do not own an iPad. I don't want to send them my source code. Is there a way I can send them the app to run in the simulator without sending source code?
Thanks
No, you cannot send them a Simulated binary. Xcode installs the application just as AppStore would, by assigning a GUID. You could possibly send the whole folder that contains your app (including the Documents folder, Library, etc.) That may possibly work. If your friends have iPads, you can always build for Ad-Hoc and let them test that way.
Related
I have created an iPhone application. I don't have the iPhone and I want to test the application on the iPhone of my friend who is far from me. How can I test it on his iPhone?
When I searched on google, it told me that you need to have the device with you. Is it possible to send the wrap and send the application to a remote location and get tested from there? I also have the Apple ID and license.
Yes with a tool like TestFlight you will be able to check wether or not your will work on a device. Thus is good for acceptance testing but never for technical working of an app.
But when it comes to really testing a device is needed, there is not way around it. You should do performance testing on a device.
Also there is no way to use the debugger unless it is connected to your development machine.
If you are developing for iOS get an iOS device.
It's possible, check Test Flight:
https://testflightapp.com/
I used it in the past for the same scenario as you
You should have a device yourself for testing on, before you publish anything in the App Store. Testing in the simulator is just not the same as testing on a device.
On developer.apple.com you will need to create a Ad Hoc distribution profile. You will also need to add all the devices you want to run the app on to this profile. Once you have the profile and you have it installed in Xcode, you can run an Archive build and sign it with the distribution profile. After this you can select the archive and click on 'Distribute...' to generate a .ipa file.
Once you have this .ipa file, you could use a site like testflightapp.com to distribute the app to test-devices. (you could also just email it ;-) )
If you are looking for just a way to transfer the ipa to someone else the best simplest solution for that would be http://www.diawi.com/ or https://appsendr.com
Get the target Device UDID and add it to your testing list, Create your IPA, drag it to the site above, Done.
No need to signup or anything like that.
I like appsendr better because of the small app they provide.
Lets you drag the IPA to your tool bar and have the ipa url right in your clipboard once it's uploaded.
As part of our software development life cycle, we want to make sure that the binary we test in house before pushing to iTunes, is the same as the binary that we push to iTunes. I know that sounds really silly, but it's a matter of checks and balances in a mid size company, so that the testers can be sure the coders didn't add in anything after testing occurred.
So is there a way to run a signed/certed app on a device that's not jail broken? Or is there a way to verify that an IPW is the exact identical code in the zip that gets pushed to iTunes?
Or possibly a way to accomplish my goals with a different way?
We have a valid developer account and around 15 different devices that are not jail broken. Would prefer to test with them left stock and not jail broken.
If you compile your app for distribution using an ad-hoc profile you can later take that archive and resign it with the appstore profile and upload it.
You can't however upload an application that was compiled with an development certificate.
A binary signed to go to the App Store cannot be run on devices via the normal ways. You can test the code by having the developers create an Ad Hoc build. This will have the same functionality as the App Store version, but you can test it.
Unfortunately, when the app is recompiled for the App Store, more code can be added.
Do you not have access to the code to test? If you must, you can have them create an adhoc in front of you, test it, and then recompile for the app store all in front of you. Seems a bit overkill, however.
There is with another trick:
first test you code for functionality's, buggs in normal way.
Than push the code to AppStore, but set the release date farther with 3 weeks, while your testers are validating it is that what they tested last time or not. Somewhere here, I have read that possibility forgot where. Never tried!
I have created Map application for iPhone and I developed same Map application on iPad too by my client requirement. Now I have same Map app project but two .ipa files one for iPhone and another for iPad.
I have already put iPhone version on iTune and it showing status "waiting for review"
1>Now I want to put my iPad version app on iTune with the same project name. How this can be achieve?
2>What Setting should I do in plist file and with xib files?
If there is universal app iPhone/iPad then in app store we can see both iphone and iPad app having same project name...So in my case what steps should I follow. Plz suggest
You can't upload two binary versions of the same app under the same name.
You either have to make a universal app (meaning iPhone/iPad app in one app) or submit under another name.
Start reading this: http://developer.apple.com/library/ios/#documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/AdvancedAppTricks/AdvancedAppTricks.html
You can submit multiple apps from the same Xcode Project by using multiple Targets, and editing the Bundle ID suffix of each Target so that each Target has a unique Bundle ID. You might also want to change the Product name for each Target in the Build settings so that your apps will have different bundle file names.
Note that, unless the iPad version is different enough (uses iPad only APIs for instance) from the iPhone version, it has been reported that Apple might reject a nearly identical iPhone/iPad pair of apps and request that you submit a single Universal build instead.
If you wanted your iPhone and iPad project to be in the same app, you should have built it that way.
However, if you did specifically want a separate iPhone and iPad app, then you should make the difference clear in the names of each app.
There are many companies who have both iPhone and iPad apps on the appstore. Generally, the iPhone app is just called 'appName' and the iPad version is usually called 'appName for iPad'.
Examples of this are:-
Skype and Skype for iPad
Ebay and Ebay for iPad
If you want the application to have the exact same name in iTunes Connect, you will have to make it a universal app.
You can cancel the "waiting for review" and submit your universal binary instead:
Can I reject a binary that has already been submitted for review?
Yes. You are permitted to reject your binary, to remove it from the
Apple review queue, when your app is in one of the following iTunes
Connect states:
Waiting For Review
In Review
To reject your binary, simply click the Reject Binary button. After
the binary has been rejected, you can then indicate you are ready to
submit another binary through Application Loader, by clicking on the
Ready to Upload Binary button.
Please note that if you reject a binary that is Waiting For Review or
In Review, your review time will be reset and you will start over from
the beginning once you submit a new binary.
iTunes Connect FAQ
However, if you absolutely need to have two seperate applications, you can create a new app in iTunes Connect and name it for example "[your app] for iPad" or "[your app] HD" or something similar like a lot of apps you see on the store.
Are there any particular reasons you aren't submitting a universal application ?
It would have been better if it was a universal app.
In itunes Connect you cant create/re-use apps-name,sku number,bundle-identifier. You could submit a universal app as update.
If you still want multiple apps, Then you will have to create multiple apps in itunes connect with different name, sku number and bundle-id,
But note one thing the name of the application installed in the device is what you give on xcode, not the one in itunes connect. So I guess you could only give that much similarity.
PS if create a app with details{apps-name,sku number,bundle-identifier} and you delete without publishing also, you cant reuse these again.
So tell client the best(may be only possible) solution is Universal app.
if you have the same application for both iphone and ipad, for iphone app name will be - [appliction name], for ipad it should be - [application name ] HD
I have finally gotten my first app to work properly and I'm attempting to send it to the App Store. In my Application Loader, I'm getting this error:
Info.plist does not contain a CFBundleResourceSpecification
I have read on the following SO question that this could be because I am Building on the simulator and then zipping up the app, and sending this instead of building on a proper device.
http://stackoverflow.com/questions/2180201/cant-upload-application-binary-to-the-app-store
However, when I provision a distribution profile, I can't select my IPod Touch under my devices when I have App Store selected. When I switch it to AdHoc I can select it, then I can Build it on the device perfectly, everything works. Has anybody had this issue before?
Any advice would help me here, Thanks!
An App Store build can't be run on a device using Xcode. It's only good for submission.
I would like to send someone the Xcode simulator version - not the device version - of my iPad app. I have located the .app file in the Finder. Do I just zip it up and send it off or is it more complicated than that?
Thanks,
Doug
UPDATE
Chrisbtoo got the answer on this one however he left of some critical bits for those of you trying this at home:
Path to Xcode simulator (the simulator can be run standalone.):
/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone Simulator.app
Path to app that appears in the home screen of the simulator:
/Users/turner/Library/Application Support/iPhone Simulator/3.2/Applications/{GUID}
It is instructive to watch what happens in the app simulator directory as you build for simulation, delete apps from the simulator desktop and generally use the simulator as an actual device.
Bottom line: This is a viable approach for sharing apps in a "simulated" ad hoc manner without the mind numbing, soul sucking process of true ad hoc app sharing.
Cheers,
Doug
Assuming the other person already has the simulator installed, you can just zip up the stuff under ~/Library/Application Support/iPhone Simulator/3.2/Applications/{GUID} (includes both the .app and any data directories needed) and send it to them - they'll need to unzip it under that same directory. What I've done in the past was to rename the {GUID} part to a more friendly name - the sim will still pick it up.
If they don't already have the simulator, they will need to sign up for a free iphone dev account and download Xcode, etc.
We just put up a little tool that will help you with this. It manages both what you need on the dev side and also the tester.
Here it is
http://blog.placeit.net/ios-app-packager/
It basically creates a little zip that you can pass to the tester and it'll install the app in the right directory and also open it up for the user with the right device selected.
I would think you want to send the entire project folder to the other person- presumably you are expecting them to open it in their XCode- and presumably they have the sdk for the app.
You have to distribute via AdHoc or App Store for beta testing.
Become a developer and then look into how to do this.
You need to have a provisioning profile, and then select the UDID's for the device you want to beta test to.
Go to the iPhone Provisioning Portal
and here is a document with more detail