Bug 50054 - Xamarin.UITest Code Signing Failed on iOS App with Safari Extension
Summary: Xamarin.UITest Code Signing Failed on iOS App with Safari Extension
Status: RESOLVED DUPLICATE of bug 48276
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 10.2 (iOS 10.1)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-12-14 20:27 UTC by Neal
Modified: 2017-01-04 23:59 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Neal 2016-12-14 20:27:08 UTC

Using Xcode 8.2 and Xamarin UITest 2.0.3 and unable to run as my safari extension is being reported as not signed. Trying to run UI Tests on an iOS 10.2 Simulator.  


14-Dec-2016 13:38:55 /Users/Neal/bamboo-agent-home/xml-data/build-dir/TEST-AIV-JOB1/apdl-ios/APDL.iOS/bin/iPhoneSimulator/Debug/apdl.app/PlugIns/ScheduleImporterAction.appex: code object is not signed at all
14-Dec-2016 13:38:55 === STDERR ===
14-Dec-2016 13:38:55 === STDERR ===
14-Dec-2016 13:38:55 Could not find any Provisioning Profiles suitable for resigning
14-Dec-2016 13:38:55 Could not resign app bundle at path:
14-Dec-2016 13:38:55 Error resigning sim bundle
14-Dec-2016 13:38:55 In architecture: x86_64
14-Dec-2016 13:38:55 with command:
14-Dec-2016 13:38:55 at Xamarin.UITest.iOS.iOSAppLauncher.LaunchAppLocal (Xamarin.UITest.Configuration.IiOSAppConfiguration appConfiguration, Xamarin.UITest.Shared.Http.HttpClient httpClient, System.Boolean clearAppData) [0x0020a] in :0 
14-Dec-2016 13:38:55 at Xamarin.UITest.iOS.iOSAppLauncher.LaunchApp (Xamarin.UITest.Configuration.IiOSAppConfiguration appConfiguration, Xamarin.UITest.Shared.Http.HttpClient httpClient, Xamarin.UITest.TestCloud.TestCloudiOSAppConfiguration testCloudAppConfiguration, Xamarin.UITest.Shared.Http.HttpClient testCloudWsClient, Xamarin.UITest.Shared.Http.HttpClient xtcServicesClient, System.Boolean testCloudUseDeviceAgent) [0x0007a] in :0 
14-Dec-2016 13:38:55 at Xamarin.UITest.iOS.iOSApp..ctor (Xamarin.UITest.Configuration.IiOSAppConfiguration appConfiguration) [0x00302] in :0 
14-Dec-2016 13:38:55 at Xamarin.UITest.Configuration.iOSAppConfigurator.StartApp (Xamarin.UITest.Configuration.AppDataMode appDataMode) [0x00017] in :0 
14-Dec-2016 13:38:55 at APDL.UITests.iOS.ValidationTests.ConfigureSimForTestSession () [0x00042] in <81c560d887964e288c223df7e9874840>:0 
14-Dec-2016 13:38:55 at APDL.UITests.iOS.ValidationTests.BeforeEachTest () [0x0000d] in <81c560d887964e288c223df7e9874840>:0 
14-Dec-2016 13:38:55 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
14-Dec-2016 13:38:55 at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00038] in <8f2c484307284b51944a1a13a14c0266>:0 
14-Dec-2016 13:38:55

Any help to get around the signing issue is appreciated.  Possibly related to Bug ID 48276

Thank you,

Neal Culiner

=== Xamarin Studio Business ===

Version 6.1.2 (build 44)
Installation UUID: 4c0dde83-004a-41d2-a792-46ee8162cf79
	Mono 4.6.2 (mono-4.6.0-branch/08fd525) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 406020007

=== NuGet ===


=== Xamarin.Profiler ===

Not Installed

=== Apple Developer Tools ===

Xcode 8.2 (11766)
Build 8C38

=== Xamarin.iOS ===

Version: (Xamarin Business)
Hash: 44931ae
Branch: xcode8.1
Build date: 2016-11-01 20:52:28-0400

=== Xamarin.Android ===

Version: (Xamarin Business)
Android SDK: /Users/neal/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.4 (API level 19)
		5.1 (API level 22)
		6.0 (API level 23)
		7.0 (API level 24)

SDK Tools Version: 25.2.4
SDK Platform Tools Version: 25.0.2
SDK Build Tools Version: 25

Java SDK: /usr
java version "1.8.0_112"
Java(TM) SE Runtime Environment (build 1.8.0_112-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.112-b16, mixed mode)

Android Designer EPL code available here:

=== Xamarin Android Player ===

Not Installed

=== Xamarin.Mac ===

Version: (Xamarin Business)

=== Build Information ===

Release ID: 601020044
Git revision: 0ccfcd52b95305ebd5b7eca0d88c1017035910ae
Build date: 2016-10-28 15:12:43-04
Xamarin addins: a39a869d8a78d87bdc6775f696c13a4cc9024501
Build lane: monodevelop-lion-cycle8

=== Operating System ===

Mac OS X 10.12.2
Darwin Neals-iMacR.local 16.3.0 Darwin Kernel Version 16.3.0
    Thu Nov 17 20:23:58 PST 2016
    root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64

=== Enabled user installed addins ===

Redth's Addins 1.0.2
Comment 1 Vincent Dondain [MSFT] 2017-01-03 15:49:45 UTC
Hi Neal,

You mentioned it: "Possibly related to Bug ID 48276", and yes unfortunately it is an exact duplicate of 48276.

This still seems to be an issue that the Test Cloud/UITest team is investigating, hence why we created a ticket on their bug tracker (which is not bugzilla).

I apologize for the lack of news, it's all private...

The only workaround I can recommend for now it to unload the extension(s) in order to UI test the main iOS app.

I asked the team to report progress on the forum (which is public) as I understand this can be frustrating.

Stay tuned.


*** This bug has been marked as a duplicate of bug 48276 ***