I understand that we need to be patient and wait on docs/blog posts on the new features.
But I do have a question regarding the new minimum iOS 4.3 support.
Does this mean we need to change all our our build.config’s and change them to 4.3 instead of 3.2 or 3.1
do we have analytics on how many devices we are now loosing who have not upgraded to 4.3?
[import]uid: 19626 topic_id: 19216 reply_id: 319216[/import]
I’d guess yes to the build.settings change … Though I wonder if we have nothing in there, if it just defaults to Corona’s minimum?
And yeah, I’m super curious on the metrics, too. As of 11/30, it was 88% on 4.3 …
http://www.marco.org/2011/11/30/more-ios-device-and-os-version-stats-from-instapaper
That’s a really slow move from 8/13 when it was 82.5%…
Granted, Apple’s talking about selling 200 million new iPhone’s next year… Still chopping out 10% off my sales numbers for some period using the new builds doesn’t make me eggggstatic or anything. 
[import]uid: 13859 topic_id: 19216 reply_id: 74103[/import]
Yeah, the 4.3 minimum made me almost spill my morning coffee.
I don’t have any analytics with my Corona apps, however with my other apps I have a significant number of pre-4.3 users.
If I do a rough breakdown of pre-4.3 it’s something like this:
4.0-4.2: 18-20%
3.1: 5-8%
Again these are numbers from my other apps, I don’t know the breakdown of my Corona apps.
[import]uid: 70847 topic_id: 19216 reply_id: 74106[/import]
How Push Notifications works? [import]uid: 55808 topic_id: 19216 reply_id: 74107[/import]
As I illuded to in my top post, documentation is still being worked on according to Carlos in a post about the Facebook single sign on. So I didn’t want to push that question since the answer was already stated implicitly. [import]uid: 19626 topic_id: 19216 reply_id: 74109[/import]
I’m also curious about that minimum ios 4.3 change…
As far as I know, once you have submitted your app with 3.2 support (as I did in my app) you’ll need to keep that with all updates. Apple does not allow dropping support for previously supported devices in app updates.
So is that mean, I wouldn’t be able to submit an update to my app if I use build 706+ ?? [import]uid: 10478 topic_id: 19216 reply_id: 74160[/import]
@PixelEnvision
Really?? I don’t think so.
As long as you specify the minimum iOS requirement in the Info.plist you should be OK.
[import]uid: 70847 topic_id: 19216 reply_id: 74174[/import]
I’m sure I’ve seen OS version restriction somewhere, still looking for the source, but the following says pretty much the same since armv6 support is also dropped… 
https://itunesconnect.apple.com/docs/iTunesConnect_DeveloperGuide.pdf
Appendix C: Device Compatibility Matrix
You are permitted to expand your device requirements only. Submitting an update to your binary to restrict your device requirements is not permitted. You are unable to restrict device requirements due to the fact that this action will inhibit customers who have previously downloaded your application to run new updates. [import]uid: 10478 topic_id: 19216 reply_id: 74175[/import]
@PixelEnvision I dont remember if i read anything about this apple policy , but I have seen many applications on the store that stops working on some devices after an update.
So I hope we can do what you said.
cheers, deniz. [import]uid: 11686 topic_id: 19216 reply_id: 74177[/import]
ah regarding to this apple doc… this is some serious bad news… [import]uid: 11686 topic_id: 19216 reply_id: 74178[/import]
Maybe you can ask Apple about that.
I think Carlos or someone from Ansca staff will tell us why this requeriment. I’m almost sure is for the new features on push notifications and gamecenter support. [import]uid: 55808 topic_id: 19216 reply_id: 74179[/import]
Yeah, but for me that means device requirements, as in camera, gps etc. Not iOS requirements.
Changing the minimum iOS version doesn’t violate this paragraph since the update will only be visible to users that have the specified iOS version or higher. Users that have a lesser iOS version will never see the update and can happily use the old version. [import]uid: 70847 topic_id: 19216 reply_id: 74181[/import]
If you look at this list
http://en.wikipedia.org/wiki/List_of_iOS_devices
4.2.1 should be the minimum because that is the last Arm7 compatible device (iPod 2nd generation) [import]uid: 8697 topic_id: 19216 reply_id: 74182[/import]
Doing a search on google for “deployment target” “app update” reveals few discussions that suggests submitting an update might be approved but either it may not be visible users with old devices or they might not be able to run it.
I also think it might be related to those but why 4.3? 4.0 also have those (if I’m not mistaken) features and making 4.3 minimum leaves out that rather large base of 4.0-4.2 users as @ingemar posted above…
Anyway, as you said Ansca will probably comment on that, let’s wait & see… [import]uid: 10478 topic_id: 19216 reply_id: 74183[/import]
PixelEnvision: My personal experience is that apps do in fact drop support of old devices in upgrades. I have an original iPhone. It is too dangerous for me to upgrade any apps because none of the apps work on this device anymore and I have to go to my Time Machine backup to get them back.
[import]uid: 7563 topic_id: 19216 reply_id: 74186[/import]
cublah: You misread the chart. The iPod 2G is an armv6 device. There is a difference between armv7 and arm7. An arm11 is actually an armv6. arm7 is apparently an armv4 or v3.
All iOS armv7 devices can run iOS 5 (and it’s a free upgrade).
[import]uid: 7563 topic_id: 19216 reply_id: 74187[/import]
robmiracle: Normally, the MinimumOSVersion should be set by us by default and you shouldn’t need to change it unless you need to specify a higher version than we do. However, it looks like we have a bug at the moment and it is still set to 3.1. This will be fixed. You can temporarily override it to 4.3, or wait for us to fix it.
[import]uid: 7563 topic_id: 19216 reply_id: 74189[/import]
Yes, my bad. I even knew that as well…doh! [import]uid: 8697 topic_id: 19216 reply_id: 74190[/import]
@PixelEnvision, you can definitely up the minimum os version. Just look at any of the old school original apps, like “Bubbles”. If you couldn’t increase, all of the “first” apps in the store would be stuck at the oldest iOS version.
[import]uid: 13859 topic_id: 19216 reply_id: 74215[/import]
Essentially, we have to keep the current release for apps that were released just to be sure… But there is a stable build archive, so what would be the problem there?
It just means using new features means relasing new Apps?
I actually just prouded myself on releasing an App with acorona that would run on all the old hardware that little kids use to get from fathers, older brothere and sisters, oh, and of course, moms … [import]uid: 5822 topic_id: 19216 reply_id: 75635[/import]