I have a problem with an app that works perfect on my iPhone 4, and on my 3Gs but both are on iOS 4. BUT, when a colleague installed it on his 3G with 3.1.2 on it... it crashes on startup.
Is there someway I can test to install the app in a 3.1.2 simulator of some kind?
He didn't send me his crash logs yet.
Best regards,
Paul Peelen
I haven't done this for the simulator, but you can find links for the old SDKs here:
http://chris-fletcher.com/2010/08/28/howto-install-iphone-sdk-2-0-3-1-for-xcode-3-2/
You should be able to install the old simulator SDKs and have them show up in the simulator menu.
Dealing with multiple SDKs has proved to be extremely painful in my experience. If you end up installing an old SDK, I'd recommend you install it in a separate "Developer" folder.
In my opinion, the best way to deal with 3.x debugging is to get your hand on an old iPod touch with 3.x installed. You can get one for pretty cheap from a local classified ads site and it really makes 3.x debugging a lot easier.
Related
I'm trying to install my iOS app on to devices running iOS 7.0. I can install them on my iPhone 4 with iOS 5.1 jailbroken. But currently I'm not able to do so on a friend iPad 4 with iOS 7.0.
For installing them on JB devices I'm using JailCoder .
It works without any problem and I can code and compile my test apps, and put them on JB devices without any effort.
Recently trying to investigate possibilities I found an application named PP25 for Windows, it is a chinese application and it is said to be able to install cracked apps on NON-JB devices.
So i tried to see ig it works somehow, I was able to get my apps converted as ipas from my phone and download them to desktop with it, and i can then upload on other JB devices, thanks to a Cydia application named AppSync, pretty good indeed, but I tried and wasn't able to install them on iOS 7.
That was disappointing, I made additional tests and it appears that the PP Assistant application is able to install cracked apps on iOS 7.0 too, but not my unsigned apps (fails to verify the app rights).
Indeed there is a section in the chinese application where you can download and install commercial apps on iOS 7.0, so there must be a trick they use to re-sign the apps to make it appear as it's a legit app and thus be able to upload to the device even if not jailbroken.
If someone has any idea of what they actually do to make this happen, this would be very useful to know to test apps without JB on every device.
Non-jailbroken devices require valid code-signing to execute binaries. Either wait for a jailbreak to surface for iOS7.X, or find a code-signing service (they are available out there).
Using Xcode 7, you can install your app to your device using a freely available Apple ID.
Free On-Device Development
Now everyone can run and test their own app on a device—for free. You can run and debug your own creations on a Mac, iPhone, iPad, iPod touch, or Apple Watch without any fees, and no programs to join. All you need to do is enter your free Apple ID into Xcode. You can even use the same Apple ID you already use for the App Store or iTunes. Once you’ve perfected your app the Apple Developer Program can help you get it on the App Store.
See Launching Your App on Devices for detailed information about installing and running on devices.
Source
I just upgraded to xCode 4.3 and used it to generate a new revision of an iPad app about 50 beta testers have been using for several months. I distributed the beta app through TestFlight as usual.
Most testers upgraded with no problem, but several testers are getting the TestFlight message "You have not permitted this device to install this build" when they try to install the new rev. I've never seen this message before. Their iPad UDID is definitely in the build's embedded.mobileprovision file and everything was working working fine with the prior revision.
What am I -- or the testers -- doing wrong and how do we correct it?
Hi i experienced the same and it seems that you must generate your mobile provisioner profile from Xcode(instead of Apple dev site for example) and you should update your App permissions (TestFlight) with this same provisioner profile that you just generated on your machine so basically the machine that generates and archive the apps using Xcode must generate the provisioner profile and then you should update your testflight app permissions with this file.
Does that make any sense?
Hope this works for you testflight is really nice to use, i faced same problems with all of my apps and hardware devices (testers all around the world)
Thanks
Turns out this is apparently a bug in Testflight. I tried to resolve the issue through their support forum and multiple emails with no real answer. I did not want to switch services as my testers knew the Testflight system well. But eventually switched to Diawi. My testers were able to install the app using Diawi with no problems.
Just a quick q about iOS development..
I'd love to be able to run a certain game emulator on my iPad..
If it's released under open source is there any thing stopping me from compiling it and running it in an emulator or getting a provisioning profile and running it on my device?
Do jailbroken apps tend to use libraries that wont run on a vanilla copy of iOS?
I.e. Do they patch the kernel to get full control of the video controller etc..
Thanks
Daniel
I think the jailbroken apps can utilize eglibc or glibc, as when I jailbroke me iPod Touch, I remember looking over the installed packages, and remember seeing something along the lines of glibc.
In short, I think if the app is self-sufficient, you probably could package it with XCode, but if it requires some low-level APIs and libraries, you're out of luck.
Ok, there have been some questions alluding to this before, and I've even read some second-hand reports of people successfully doing this, but so far I haven't found a concrete answer.
Basically, I want to build an application for simulator using iOS 4.x, and then run it on a 3.x simulator.
I have both SDKs installed, so all I need is the last mile of getting the app to show up in the 3.x simulator.
I tried just copying the app across from Library/Application Support/iPhone Simulator/4.2/Applications to Library/Application Support/iPhone Simulator/3.0/Applications but it doesn't show up when I load the 3.x simulator. There's a binary plist called applicationstate.plist, which I'm guessing keeps track of what apps are installed on the simulator, but I don't know what the binary format is so I'm kind of stuck at this point.
Has anyone managed to load a 4.x app onto a 3.x simulator? And if so, how did you do it?
Why are you even trying to do this? What are you trying to achieve? If what you really just want to do is ensure the app works on iOS 3.x then simply state that in xcode and don't worry about the actual simulator. The simulator could be running iOS 5.0 for all you should care as long as you have set 'iOS Deployment Target' to '3.0' in xcode's project settings. That will ensure the application is compatible with iOS 3.x and above. Obviously you then still need to ensure you're not calling methods from SDK 4.x when it will run on an iOS 3.x device. If that is what you're trying to test then what you're doing won't actually work. You should (as Apple advises) always grab hold of a real device running the target firmware version and test it on that. Grab an old iPod for example with iOS 3.x and try testing your app on that to ensure you haven't called iOS 4.x methods when running under an older firmware.
The answer is: No, you cannot build for 4.x simulator and run on a 3.1.x simulator or earlier due to fundamental changes in the way the simulator works.
The only way to test 3.x support is to either run it on a 3.x device (after setting min deployment target), or build on an older xcode that supports 3.x simulator (which isn't feasible if you use Xcode 4, except for iPad 3.2).
Note: Setting the deployment target does not test compatibility with older operating systems. It's the operating system that it actually RUNS on that matters (such as "iPhone 4.3 Simulator", "iPhone 4.0 Simulator", "iPad 3.2 Simulator", or an actual device).
Of course, now that 3.x users make up less than 10% of the total population, it's not really worth the trouble to support it anymore.
This question already has answers here:
Closed 12 years ago.
Possible Duplicates:
iPhone development on PC
iPhone development on Windows
Do I really need a Mac to make small simple apps for iPad? Is there any kind of work around? Cool IDE?
Yes, you need an Intel-based Mac to develop for iPhone/iPad if you want to do so with their native SDK.
There are workarounds, a few of which are listed here but they may be rendered unusable with the latest version of iPhone OS since they will soon disallow just about anything that doesn't use the native SDK
I wasn't going to post it, but you did say any reply :)
Browser based (safari compatible) apps would be one "work around". I know it's a weak answer, but sometimes people miss the obvious answers so there you go.
Yes. And you can use Xcode IDE
You will likely need OS X.
Both Monotouch and XCODE run on OS X.
If you can get OS X to run on a non-Mac then no, you don't need a Mac.
However, realistically... yes you do.
The iPhone and iPad SDK relies on code that comes packaged with the Mac OS. If you want to build legitimate applications and have the possibility of listing those apps in the iTunes store, you must build them on a Mac.
There are ways around this to build apps that will never be distributed ... but those methods tend to be highly illegal.
You can still develop iPhone/iPad WebApps that look like native apps on pretty much any web development platform/toolset.
While I am not an attorney, based upon the new SDK agreement, I believe you can use HTML, CSS, and JavaScript to create native iPhone/iPad apps. There is actually a book already there that talks about how to do that. Here is the book, http://www.amazon.com/Building-iPhone-Apps-HTML-JavaScript/dp/0596805780/ref=sr_1_1?ie=UTF8&s=books&qid=1274474001&sr=8-1
If you want to create small simple apps for iPhone/iPad, you can create a Web app that runs in Safari using HTML. You can actually create fairly slick apps with this method and make them look like native apps. I've create some using jQTouch and they look like native apps. You can test them either in Safari on Windows or on your iPhone or iPad.
It wouldn't be easy to develop an iPhone/iPad application on Windows. You would have to install OSX86 on your PC, or run a virtualized OSX install through vmware if possible. Apple is incredibly restrictive on software provisioning and app store approval, so you may have a hard time testing and releasing your app later on. For these reasons and more, I'm switching to Android development.