Bug 1257 - TweetStation does not run on the device, error message appears.
Summary: TweetStation does not run on the device, error message appears.
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-10-05 12:00 UTC by Jatin
Modified: 2011-10-14 08:49 UTC (History)
3 users (show)

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

Screenshot for the bug. (216.36 KB, image/pjpeg)
2011-10-05 12:00 UTC, Jatin

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 Jatin 2011-10-05 12:00:11 UTC
Created attachment 597 [details]
Screenshot for the bug.

Steps to reproduce:

1.Check out the tweetstation code from github here: https://github.com/migueldeicaza/TweetStation
2.Open the .sln file in MonoDevelop
3.Build and deploy to the device.
4.Build error appears.

Actual result:

When try to run tweetstation on the device, it gives the build error. Refer to the attached screenshot.

Note: When try to run any other solution on the device, it builds successfuly.

Expected result:

It should successfuly get build and depoyed to the device, the way it does with the simulator.


Mac 10.7 (Lion)
MonoTouch 4.9.6
iPhone 4
Comment 1 Alan McGovern 2011-10-06 07:03:30 UTC
This is because your provisioning profile is not a generic one which can sign arbitrary applications. How did you generate it? You can work around this by simply deleting the bundle identifier from the plist file by using the plist editor (double click on Info.plist) and then a correct one will automatically be generated for you.
Comment 2 Atin 2011-10-14 08:49:12 UTC
I tried to follow the above comments, and it works.

Hence, closing this issue.