- Home
- Forum
- Xamarin.Android
- i used sftabview but debug console message displayed.
i used sftabview but debug console message displayed.
sftabview version is v17.1.0.38
show below in debug console
and so xamarin app very slow
public MainPage()
{
InitializeComponent();
SfTabView tabView;
tabView = new SfTabView();
var allContactsGrid = new Grid { BackgroundColor = Color.Red };
var favoritesGrid = new Grid { BackgroundColor = Color.Blue };
var contactsGrid = new Grid { BackgroundColor = Color.Green };
var alternativeGrid = new Grid { BackgroundColor = Color.Olive };
tabView.TabHeaderPosition = TabHeaderPosition.Bottom;
tabView.OverflowMode = OverflowMode.DropDown;
var tabItems = new TabItemCollection
{
new SfTabItem()
{
Title = "CEO",
Content = allContactsGrid
},
new SfTabItem()
{
Title = "Patients",
Content = favoritesGrid
},
new SfTabItem()
{
Title = "Staff",
Content = contactsGrid
},
new SfTabItem()
{
Title = "Alternative",
Content = alternativeGrid
}
};
tabView.Items = tabItems;
this.Content = tabView;
}
}
04-19 15:13:52.942 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:52.949 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:52.962 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:52.979 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:52.996 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.013 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.030 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.046 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.062 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.079 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.096 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.112 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.152 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.687 D/ViewRootImpl@dfb5b06[MainActivity]( 8037): ViewPostIme pointer 0
04-19 15:13:53.734 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.749 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.766 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.774 D/ViewRootImpl@dfb5b06[MainActivity]( 8037): ViewPostIme pointer 1
04-19 15:13:53.790 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.797 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.814 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.829 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.846 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.863 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.879 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.896 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.912 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.929 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.946 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:53.963 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
04-19 15:13:54.001 E/balWebApp.Droi( 8037): Invalid ID 0x00000000.
i
SIGN IN To post a reply.
5 Replies
RS
Ruba Shanmugam
Syncfusion Team
April 22, 2019 11:05 AM UTC
Hi Kichoul,
Greetings from Syncfusion.
We have created a sample as per your provided code snippet with SfTabView and we are not able to reproduce the log you have mentioned in the output window. The error seems to be related to Resource files used in the Application.
Can you please whether it appears only when the TabView is used and if possible share us the sample which will be helpful for us to validate the issue.
We have attached the sample we have created which is available in the below link.
sample:
http://www.syncfusion.com/downloads/support/directtrac/general/ze/TabViewSample1000471110
Please let us know if you have any concern.
Regards,
Greetings from Syncfusion.
We have created a sample as per your provided code snippet with SfTabView and we are not able to reproduce the log you have mentioned in the output window. The error seems to be related to Resource files used in the Application.
Can you please whether it appears only when the TabView is used and if possible share us the sample which will be helpful for us to validate the issue.
We have attached the sample we have created which is available in the below link.
sample:
http://www.syncfusion.com/downloads/support/directtrac/general/ze/TabViewSample1000471110
Please let us know if you have any concern.
Regards,
Ruba Shanmugam.
KI
kichoul
April 23, 2019 09:32 AM UTC
Thank you for your answer.
I tried to run the attached file.
So I looked like the attached log.txt file.
Likewise, 04-23 09:37:52.857 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
Or, every time you drag the screen, it's created.
No other codes were attached.
I can't attach the file.
We'll send it to you via Google Drive Link.
https://drive.google.com/file/d/1g5RjRGzXgpTAUf9KS_d50uxBW_a6Otu9/view?usp=sharing
My test environment is
window 10
Visual Studio Community 2017
version 4.7.04056
Phone is samsung sm-g950N
Android 9.0 api 28
I tried to run the attached file.
So I looked like the attached log.txt file.
Likewise, 04-23 09:37:52.857 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.874 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.891 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.906 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.923 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.939 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.959 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.972 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:52.990 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:53.006 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:53.023 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
04-23 09:37:53.061 E/e.TabViewSampl(26056): Invalid ID 0x00000000.
every time somebody taps Or, every time you drag the screen, it's created.
No other codes were attached.
I can't attach the file.
We'll send it to you via Google Drive Link.
https://drive.google.com/file/d/1g5RjRGzXgpTAUf9KS_d50uxBW_a6Otu9/view?usp=sharing
My test environment is
window 10
Visual Studio Community 2017
version 4.7.04056
Phone is samsung sm-g950N
Android 9.0 api 28
RS
Ruba Shanmugam
Syncfusion Team
April 23, 2019 10:46 AM UTC
Hi Kichoul,
Thanks for your patience. We have checked the reported issue “SfTabView displayed invalid ID message in debug console” in android version 9.0.
We were able to reproduce the reported issue and we have fixed this issue and attached the patch file for your reference. Please find it from the below link.
Please find the patch setup from the below location.
http://syncfusion.com/Installs/support/patch/17.1.0.38/1084300/F144115/SyncfusionPatch_17.1.0.38_1084300_4232019050327020_F144115.exe
or
Please find the patch assemblies from the below location.
http://syncfusion.com/Installs/support/patch/17.1.0.38/1084300/F144115/SyncfusionPatch_17.1.0.38_1084300_4232019050327020_F144115.zip
or
Please find the NuGet from the below location.
http://syncfusion.com/Installs/support/patch/17.1.0.38/1084300/F144115/SyncfusionNuget_17.1.0.38_1084300_4232019050327020_F144115.zip
Assembly Version: 17.1.0.38
Disclaimer:
Please note that we have created this patch for version 17.1.0.38 specifically to resolve the following issue reported in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.
The fix for this issue will be included in our next weekly nuget release, which will be available on 30th April 2019.
Thanks for your patience. We have checked the reported issue “SfTabView displayed invalid ID message in debug console” in android version 9.0.
We were able to reproduce the reported issue and we have fixed this issue and attached the patch file for your reference. Please find it from the below link.
Please find the patch setup from the below location.
http://syncfusion.com/Installs/support/patch/17.1.0.38/1084300/F144115/SyncfusionPatch_17.1.0.38_1084300_4232019050327020_F144115.exe
or
Please find the patch assemblies from the below location.
http://syncfusion.com/Installs/support/patch/17.1.0.38/1084300/F144115/SyncfusionPatch_17.1.0.38_1084300_4232019050327020_F144115.zip
or
Please find the NuGet from the below location.
http://syncfusion.com/Installs/support/patch/17.1.0.38/1084300/F144115/SyncfusionNuget_17.1.0.38_1084300_4232019050327020_F144115.zip
Assembly Version: 17.1.0.38
Disclaimer:
Please note that we have created this patch for version 17.1.0.38 specifically to resolve the following issue reported in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.
The fix for this issue will be included in our next weekly nuget release, which will be available on 30th April 2019.
KI
kichoul
April 24, 2019 03:59 AM UTC
Hi, Ruba Shanmugam.
After patching, it's working.
Thank you for your quick action.
After patching, it's working.
Thank you for your quick action.
MK
Muneesh Kumar G
Syncfusion Team
April 24, 2019 04:52 AM UTC
Hi Kichoul,
Glad that the issue has been resolved and please get back to us if you need any other assistance.
Thanks,
Muneesh Kumar G.
SIGN IN To post a reply.
- 5 Replies
- 3 Participants
-
KI kichoul
- Apr 19, 2019 06:20 AM UTC
- Apr 24, 2019 04:52 AM UTC