Bug 22990 - iOS and Windows Phone output is blank
Summary: iOS and Windows Phone output is blank
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-09-15 07:38 UTC by Prabakaran
Modified: 2016-03-16 12:39 UTC (History)
4 users (show)

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


Attachments
Sample (162.11 KB, application/x-zip-compressed)
2014-09-16 05:03 UTC, Prabakaran
Details


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:
Status:
RESOLVED FIXED

Description Prabakaran 2014-09-15 07:38:49 UTC
I am creating custom control for Xamarin.Forms. And i have faced the issue similar to this question,
http://stackoverflow.com/questions/25800774/ios-and-wp-blank-app-not-rendered-in-xamarin-forms-pcl.
The solution provided by "Bart" working fine for me. Anyhow the class not loaded is an issue in Xamarin.Forms. Thanks,
Comment 1 Arpit Jha 2014-09-15 08:19:49 UTC
I have checked this issue and unable to reproduce it.

I have tried following steps to reproduce it.
1.Create a Xamarin form application.
2.Add a class(Mypage.cs)
3.Call Mypage.cs in App.cs and Did some code in it using custom cotrol.
4.Run the application

I observed that application successfully deployed on ios simulator.

 public  class Mypage :ContentPage
    {

     public Mypage()
     {

         Content = new StackLayout
         {
             Children = {
        new Label {
          Text = "Hello, Custom Renderer !",
        }, 
        new Entry {
          Text = "In Shared Code",
        }
      },
             VerticalOptions = LayoutOptions.CenterAndExpand,
             HorizontalOptions = LayoutOptions.CenterAndExpand,
         };
     
     }

    }

Let me know if I missed anything to reproduce it.

Screencast regarding same :

http://screencast.com/t/ybOi3LPo58v
http://screencast.com/t/sjPyek8s6s2W

Environment Info:
VS professional 2013 Update3
XVS 3.5.58.0
Comment 2 Prabakaran 2014-09-16 05:03:42 UTC
Created attachment 8073 [details]
Sample
Comment 3 Prabakaran 2014-09-16 05:05:07 UTC
Comment on attachment 8073 [details]
Sample

Thanks for your response. Working fine for me upto you have tried. But my requirement is to add this project reference(renderer and PCL) to other xamarin forms project as a dll. Please find the attachment, I have created simple sample in Windows Phone to reproduce this issue.

Note:
Xamarin dll version – 1.2.2.0

Please let me know if you have any clarifications.
Comment 4 Prabakaran 2014-09-16 09:02:18 UTC
Same problem occur in iOS as well.
Comment 5 Prabakaran 2014-09-17 07:42:36 UTC
Hi,

Can you please update on this ASAP?

Thanks,
Prabakaran
Comment 6 Jason Smith [MSFT] 2016-03-16 12:39:09 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
 
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d

Warm regards,
Xamarin Forms Team