• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Unit tests bundle with bad code signature (Xc7b6)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unit tests bundle with bad code signature (Xc7b6)


  • Subject: Re: Unit tests bundle with bad code signature (Xc7b6)
  • From: Ben Kennedy <email@hidden>
  • Date: Mon, 14 Sep 2015 15:53:07 -0700

To continue this dialogue with myself: I discovered that the problem was solved by providing an Info.plist for the test target, something which (for some reason) had been missing for a very long time. Its absence was clearly insignificant in the simulator, and on hardware devices at some prior point in time.

I still don't know what the .xctestconfiguration file is, or why it gets put there, so the essence of the original bug holds.

b

> On 09 Sep 2015, at 4:13 pm, Ben Kennedy <email@hidden> wrote:
>
> No takers, huh?
>
> This seems to be trivially easy to reproduce in a brand-new app using solely the Xcode-provided template.  Unit tests simply fail to deploy to a real device.  Behaviour is no different under Xcode 7 GM released today.
>
> Filed as rdar://22634495; http://openradar.appspot.com/22634495.
>
> I haven't been able to find any meaningful discussion of what the .xctestconfiguration file even is.
>
> b
>
>
>> On 04 Sep 2015, at 5:24 pm, Ben Kennedy <email@hidden> wrote:
>>
>> Hey folks,
>>
>> I'm trying to get my UT suite running on a physical device, and I'm hitting a wall with Xcode apparently producing an uninstallable test bundle.
>>
>> Seems Xcode is putting some kind of .xctestconfiguration file into the .xctest bundle after code-signing it, thereby rendering it invalid; when I try to run tests on device, it never launches (alert saying "App installation failed. The application does not have a valid signature.").
>>
>> This is confirmed using `codesign -v`:
>>
>>> retinafey:Kashoo ben$ codesign -vv ./build/Kashoo/Build/Products/Development-iphoneos/KashooLogicTestsDev.xctest
>>> /Users/ben/Documents/Kashoo-iPad/Kashoo/build/Kashoo/Build/Products/Development-iphoneos/KashooLogicTestsDev.xctest: a sealed resource is missing or invalid
>>> file added: /Users/ben/Documents/Kashoo-iPad/Kashoo/build/Kashoo/Build/Products/Development-iphoneos/KashooLogicTestsDev.xctest/KashooLogicTestsDev-35241011-6B88-46C6-8617-DAC1C18B965E.xctestconfiguration
>>
>> If I delete the .xctestconfiguration file, `codesign -v` then passes. Of course, it's too late at this point.
>>
>> Any tips?
>>
>> thanks,
>>
>> b
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Xcode-users mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Unit tests bundle with bad code signature (Xc7b6) (From: Ben Kennedy <email@hidden>)
 >Re: Unit tests bundle with bad code signature (Xc7b6) (From: Ben Kennedy <email@hidden>)

  • Prev by Date: Re: Creating segues
  • Next by Date: Re: Creating segues
  • Previous by thread: Re: Unit tests bundle with bad code signature (Xc7b6)
  • Next by thread: IBOutlet Connection Problem
  • Index(es):
    • Date
    • Thread