Bug 38559 - Fitpulse and Industrial theme samples won't start on simulator.
Summary: Fitpulse and Industrial theme samples won't start on simulator.
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: David Humphreys
Depends on:
Reported: 2016-02-09 02:48 UTC by Jon Goldberger [MSFT]
Modified: 2016-03-13 22:01 UTC (History)
1 user (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 for Bug 38559 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Jon Goldberger [MSFT] 2016-02-09 02:48:53 UTC
## Description

When trying to run the Fitpulse and Industrial sample apps from the Component package, the app failed to start on the simulator. Adding x86_64 support in the Project Options->iOS build page partly resolved the issue in Xamarin Studio (Mac) and fully resolved it in Visual Studio. 

I say "partly" in Xamarin Studio  because there is another bug I will be reporting about some strange ghost breakpoint issue. IN Xamarin Studio, in addition to adding support for x86_64 architecture, I had to open the Breakpoints pad  (View->Debug Windows->Breakpoints) and click "Clear All Breakpoints" even though none were showing in the pad. 

Side note: I ran into this ghost breakpoint issue last week in one of my own sample apps as well, but was not able to reproduce until now. In that case I also had to add support for x86_64 architecture as above (it was an old sample). 

## Steps to reproduce

1. Download the Fitpulse (or Industrial) component from:
or for Industrial:

2. Open the FitpulseTheme.Sample.iOS solution (not the Classic solution) in Xamarin Studio

3. Deploy to a simulator

Expected result: App will launch.

Actual result: App crashes immediately with no error or indication as to why, just this in the Mac OS X system console:

>2/8/16 4:41:34.967 PM com.apple.CoreSimulator.CoreSimulatorService[11215]: Error Domain=FBSOpenApplicationErrorDomain Code=1 "(null)"

4. Open the Project Options and change the iOS Build->Supported Architectures to:
i386 + x86_64

5. Clean and rebuild and deploy to the simulator again.

Expected result: App will launch.

Actual result: App hangs on start screen.

6. Open the breakpoints pad (View->Debug Windows->Breakpoints)

7. Note that no breakpoints are shown, but the Clear All Breakpoints button is enabled.

8. Click the Clear All Breakpoints button. 

9. Relaunch the app.

Expected result: App will launch.

Actual result: As expected (app launches and UI is displayed... success!)

## Environment

=== Xamarin Studio ===

Version 5.10.2 (build 56)
Installation UUID: 964c531b-d928-456b-a9ae-e1f82266b360
	Mono 4.2.2 (explicit/996df3c)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402020030

=== Xamarin.Profiler ===

Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 7.2.1 (9548.1)
Build 7C1002

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 962a050
Branch: master
Build date: 2016-01-29 16:59:11-0500

=== Xamarin.Mac ===

Version: (Business Edition)

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/apple/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.3   (API level 18)
		4.4   (API level 19)
		5.0   (API level 21)
		5.1   (API level 22)
		6.0   (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.2

Java SDK: /usr
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Xamarin Inspector ===

Hash: 1b526e6
Branch: master
Build date: Tue Nov 17 20:54:30 UTC 2015

=== Build Information ===

Release ID: 510020056
Git revision: bb74ff467c62ded42b7b7ac7fdd2edc60f8647b0
Build date: 2016-01-26 16:24:41-05
Xamarin addins: 8b797d7ba24d5abab226c2cf9fda77f666263f1b
Build lane: monodevelop-lion-cycle6-c6sr1

=== Operating System ===

Mac OS X 10.11.3
Darwin Jons-iMac.local 15.3.0 Darwin Kernel Version 15.3.0
    Thu Dec 10 18:40:58 PST 2015
    root:xnu-3248.30.4~1/RELEASE_X86_64 x86_64
Comment 1 Bill Holmes 2016-03-08 16:53:22 UTC
Fitpulse has been delisted.  If we bring it back we will need to address this issue.

I believe that the Industrial Theme is still active and probably needs to have this resolved.
Comment 2 David Humphreys 2016-03-13 22:01:39 UTC
The issue appears to be that the project file is use Arm as the architecture for the simulator build configuration not the i386 one