Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9009581
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 16, 20262026-06-16T02:14:10+00:00 2026-06-16T02:14:10+00:00

This problem has been driving us nuts for some time. We have applications, all

  • 0

This problem has been driving us nuts for some time. We have applications, all built with Titanium (I’m mentioning this because I’m not 100% sure that the problem doesn’t come from there). The applications are up on the store, we updated them a few times since the every launch.

Right now, they supports armv6 and armv7.

For the next update, we want to add support for the iphone 5, which means that we have to drop support for armv6. Which is absolutly fine. We also don’t mind setting the minimum OS version to 4.3.

So we changed the build settings in xcode to armv7 armv7s, set the minimum os to 4.3, added the retina screens and so one, builded the app. We left everything else as it were. When we try to validate the app, we get this message :

this bundle does not support one or more of the devices that were supported in the previous bundle for this app

With a link to the apple manual page : http://developer.apple.com/library/ios/#qa/qa1623/_index.html

Which told us that the error might be because :

When you see this error message, you have changed the “Targeted Device Family” build setting (which modifies the UIDeviceFamily info.plist key.)”

But we did not.

Also, a few line below (in Targeting the latest iOS):

For example, if your app is no longer built with armv6, you should not add armv7 to your UIRequiredDeviceCapabilities. This may cause Xcode or iTunes Connect to erroneously reject your update.

Of course, we did not do that.

We even tried to make to change the app version to the next major one, as someone stated it solved it.

Has anyone a clue on how we remove armv6 support for good ? The only solution we found would be to delete the application and recreate it with only armv7 this time. This, of course, would not be acceptable as we would lose comments, ratings and so on.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-16T02:14:14+00:00Added an answer on June 16, 2026 at 2:14 am

    Ok I manage to get it to work and now I’m wondering what went wrong when we tried the first times. Here is what I finaly did (nothing more):

    • took the current version in Titanium
    • Cleaned it up
    • set the version in Titanium to the next major one (2.0 in our case)
    • reseted environment to use xcode 4.5 (it was already the case, but I was willing to be on the safe side)
    • builded the package through publish, with the SDK set to 6.0
    • The build process confirmed that this was ok ([INFO] Minimum iOS version: 4.3 linked iOS Version 6.0)
    • Once done, validated the package in xcode and uploaded it

    And here are all the things I did not do this time:

    • Changed anything in the info.plist
    • Changed anything in the build architectures
    • actually anything in xcode except validate and upload
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This has been driving me nuts all day. I have a weird bug that
This has been driving me nuts all day. I've seen this problem crop up
This problem has been driving me nuts all day and there has to be
This has been driving me nuts for a week now. I have a class
So this has just been driving me nuts! I have looked through tons of
I have a javascript function that has been driving me nuts. This is the
This has been driving me insane all day and I think I have the
This problem has been driving me nuts for a while now, and I can't
I have a problem that has been driving me nuts for days.. I've tried
I have had this problem for a while and it has been driving me

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.