Skip to main content
SirRookie
Inspiring
October 6, 2016
Question

Uploading to Itunes - Invalid type for UIDeviceFamily value

  • October 6, 2016
  • 15 replies
  • 9320 views

I uploaded an IPA file today. Saw this error the first time ?!

What i know i dont have enabled Family sharing at Itunes connect.

Please help.

This is the norig Mail from Apple

Dear developer,

We have discovered one or more issues with your recent delivery for "XXXXXXXXXXXXXXXXXXXXXXXX". Your delivery was successful, but you may wish to correct the following issues in your next delivery:

Invalid type for UIDeviceFamily value - Values for UIDeviceFamily are expected to be integers.

After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.

Regards,

The App Store team

This topic has been closed for replies.

15 replies

OXWARD
Participant
November 7, 2016

WARNING ITMS-90686: "Invalid type for UIDeviceFamily value.Values for UIDeviceFamily are expected to be integers."

I can't sale My APP.

Colin Holgate
Inspiring
November 7, 2016

See my reply to the other post you made, about getting using AIR 24 instead of AIR 23.

Community Manager
November 1, 2016

Hello Everyone,

This issue has been fixed in AIR 24 beta Download Adobe AIR 24 Beta - Adobe Labs

The AIR sdk now changes string from application descriptor to integer in Info.plist in the ipa.

Thanks,

Krati | Adobe AIR Engineering

Colin Holgate
Inspiring
November 1, 2016

Can you say anything about the App Thinning problems have also seen?

Frédéric C.
Inspiring
October 31, 2016

A hotfix in AIR 23 SDK would be nice for people (like me) who don't want to publish with beta versions. Thanks!

Participating Frequently
October 21, 2016

THIS IS STILL AN ISSUE!  I tried updating a App this morning and still received the error message.  Please get this fixed right away.

ElsaPrieto
Participating Frequently
October 20, 2016

Hey, if you're struggling to upload your app to iTunes Connect, I've found a way to modify the Info.plist and resign the IPA:

- rename your IPA to ipaName.zip

- unzip the IPA

- go in the Payload folder, right click on the app, show package contents

- open the file Info.plist

- change the UIDeviceFamily item0/1 type to Number

- open a terminal, navigate to the folder where the Payload folder is, type "zip -qry whatever.ipa Payload"

- download iOS App Signer

- resign your IPA with the right certificates

I was able to upload, and submit for App Store without any warning

App runner KG
Known Participant
October 21, 2016

hi, sorry but with distribution certificate does not work. works with developer, but not with iphone distribution. thanks for the reply

ElsaPrieto
Participating Frequently
October 21, 2016

@App runner KG : what's the problem exactly ?

App runner KG
Known Participant
October 20, 2016

we have exactly the same problem. Using macOS Sierra, Application Loader 3.6, SDK 23

can't make any updates. Apple rejects also in TestFlight. When there will be a solution?

Inspiring
October 19, 2016

I have same problem.

If I upload new ipa file to iTunes connect,I can't select build target.

So I can't upgrade now!

What adobe doing now?? When can I release?

p0L
Known Participant
October 13, 2016

I currently have the same issue ( SDK 22 and 23 )

Participant
October 12, 2016

This is STILL an issue.  The complile and submission to iTunes Connect works, however, the TestFlight app will NOT let you install, says it's "not compatible".  If you take the same IPA file and install manually (using iTunes), then, this works.  But, TestFlight must also look at this key and it's failing.

PLEASE FIX ASAP!!!!

ios 10 (iPad) error on install using iTunes

ios 10 (iPhone) works

Participant
October 12, 2016

To clarify my post above, iPhone install in TestFlight works, but, does not work on iPad.

natural_criticB837
Legend
October 12, 2016

Have you tried renaming the .ipa to .zip, locating the pinfo file and changing the DeviceInfo <string> to <integer>? I do not know if the .ipa has a signature that would prevent this from working, its just an idea.

Participant
October 8, 2016

Just to note that our app went live and all good. So I think you can avoid that warning for now. Cheers