We would like to use Appcelerator Titanium to develop an IOS, Android and Blackberry OS 5.x app. I know IOS and Android are supported but is BBerry OS 5.x also supported as there's no mention of it in the docs?
There have been various preview releases over the last several years of BlackBerry support in Titanium. They've all been withdrawn, except for the most recent one, BlackBerry 10. You could hunt around the internet and perhaps find an old copy of one of the old versions (it was only released temporarily to customers), but it wouldn't be "supported", as your question stipulates it must be.
BlackBerry 10 is the only one in preview availability. The source has been released, and you can read about it on their blog:
http://developer.appcelerator.com/blog/2012/12/announcing-preview-availability-of-the-blackberry-sdk.html
Related
Some of my apps published on play store getting crashed on android version 4.4 and onwords
Same apps worked on other versions of Android.
Is this issue related to os or something else?
Yes, the issue is related to the os. From version to version features can change and old tools can no longer be supported. I recommend you look at the update log and see which old features you used that may no longer be supported.
Is it possible to update iOS simulator to the latest version of iOS? Now it is 7.0.6, but my simulator is 7.0.3, I have XCode 5.0.2 and updated all downloads in Preferences.
Apple has not released any further 7.0.X SDK than 7.0.3. The reason for that is because the API has not changed, and neither has behavior changed significantly enough to warrant a new SDK release. 7.0.6 in particular is only a security update and would not be applicable to the simulator at all; the simulator uses the underlying OS X infrastructure for network connections. You should wait for the upcoming OS X security fix.
You can, however, download beta releases of Xcode 5.1 with 7.1 beta SDK, and make sure your app is ready for the upcoming iOS 7.1 release.
the simulator is definitely still vulnerable to gotofail even on macs that have been updated with the security fix. this is easily testable by using it to browse to gotofail.com on osx 10.9.2: https://twitter.com/visnup/status/444992820915363840
The next update of my iPhone app will be targeted for iOS7 only. A couple of questions?
Does this mean I can delete all the non-retina images from my app?
If I have only retina images left do I still need to mark them #2x?
Does Apple keep older iOS versions of my app on the store so those running older versions of iOS who have bought or want to buy can still access it?
Any help would be most appreciated.
Yes you still need to have the #2x at the end. Yes you can drop all the non-retina images but could affect performance as even the newer devices will use some none-retina images but the main performance hit was to iPhone 3GS and below but as iOS 7 will not run on iPhone 3GS or below it isn't a requirement you'll just have to handle the performance issues. No Apple do not keep hold of older versions of your app on the app store, if you drop support for it then it is gone.
To answer the second part of your question YES, Apple does indeed store older versions for download.
For my app Parkable I created one for iOS5/6 then when 7 came about I specifically targeted it and dropped support for older iOS builds, now if you're not on 7+ you can still download the old version (instead of the old error telling the user to update their OS). This happens automatically as I recall, simply change your deployment target in both your project and target under the info tab.
Feel free to test if you have a pre-7 device (iPhone or iPad) and 7+ device https://itunes.apple.com/us/app/parkable/id577954935?mt=8&uo=4
We have just released a new version (v1.5) of our app on AppStore, this version was built using Xcode 4.6 using base SDK 6.1, supporting iOS 5.0 as minimum version. Now the problem is that iOS 7 users are unable to install the latest version (v1.5), however they can see 1.5 version on AppStore but when they install it they get 1.4 version.
Note: We submitted this app using Xcode 5.0 as Xcode 4.6 just got stuck in the middle...
Apple is currently reviewing apps with iOS 7 devices. So they have (with very high probability) reviewed your app on an iOS 7 device.
If the app has been recently released, then it may only be that servers need some time to refresh. If it has been a long time since the app was released (more than one day), then you should contact Apple support and ask them to see what is going wrong with their App Store system.
Unfortunately the issue was sporadic, it happens with those users who use "App Store" mobile app to install our application. App Store displays latest version in the App-Store app but when they install it they get a previous version on their devices. Then again if user launches "App Store" he is able to upgrade to the latest versions. This issue doesn't effected our existing customers but the new one (those who have deleted the app from their device also experienced similar issues). We had a long conversation with Apple on this issue over emails, finally they admitted that it was due some problem at their end.
Now it is fixed for our app and we no longer have this issue for current release. I hope this post will help to someone having similar problem.
I'm using Flash Builder 4.5 with Flex SDK 4.5.1, and when trying to deploy an app to a 2nd gen iPod Touch with latest available iOS I get an error saying the app is not valid, and according to some Adobe sites, only 1st generation iPods aren't supported. The application works fine in an iPhone.
Should I change some setting, update to AIR SDK 3.1, or am I wrong thinking my app should work on this device despite Adobe's pages?
From what I managed to gather a week ago, Adobe dropped iPod Touch 2ng Gen support with AIR 2.6 (or even 2.5, I don't know for sure).
However, one may be able to compile a Flex Mobile project targetting an old AIR SDK version (or a more recent one if you can target Flash 10.1), and then use PFI (the old packager for iPhone before it was combined with ADT) so your application works with older iOS devices.
Sadly, my current project is forced to use ANE, so I guess I must forget about supporting old devices.