1. Home
  2. Forum
  3. Blazor
  4. Exception in Debug Mode when using ProgressBar

Exception in Debug Mode when using ProgressBar

Hi Guys,

i reinstalled my system. I'm using VS 2022 v17.11.2 and Syncfusion 26.2.13. When i open and debug a project  where i use a SFProgressBar I always get the following Exception.

Error: Could not find 'sfBlazor.getElementBoundsById' ('getElementBoundsById' was undefined).
  Nachricht =
  Quelle =
  Stapelüberwachung:
  at https://localhost:7295/_framework/blazor.webassembly.js:1:328 
    at Array.forEach (<anonymous>)
    at a.findFunction (https://localhost:7295/_framework/blazor.webassembly.js:1:296)
    at _ (https://localhost:7295/_framework/blazor.webassembly.js:1:2442)
    at https://localhost:7295/_framework/blazor.webassembly.js:1:3330 
    at new Promise (<anonymous>)
    at Object.beginInvokeJSFromDotNet (https://localhost:7295/_framework/blazor.webassembly.js:1:3311)
    at Object.Gt [as invokeJSFromDotNet] (https://localhost:7295/_framework/blazor.webassembly.js:1:62569)
    at Object.Ii (https://localhost:7295/_framework/dotnet.7.0.20.hqs5bjbv9e.js:5:71974)
    at _mono_wasm_invoke_js_blazor (https://localhost:7295/_framework/dotnet.7.0.20.hqs5bjbv9e.js:14:103886)

 After a Click on Continue in VS the Progress Bar Shows up and everything works. But its annoying as hell. I even created a new Empty Wasm App and just placed a ProgressBar in Index.razor it always throws the exception. 

Can you help me get rid of it? I attached the Project with the ProgressBar to this Thread. If i start the App without Debugging it seems to work fine.

Thank you very much.
​


Attachment: BlazorSfProgressbarError_1930b99a.zip

14 Replies 1 reply marked as answer
GV Gopalakrishnan Veeraraghavan Syncfusion Team September 6, 2024 02:02 PM UTC

Hi Andreas,


We are currently analyzing your query, and we will update the status within one business days (September 9th, 2024). We appreciate your patience until then.


Regards,

Gopalakrishnan V


DG Durga Gopalakrishnan Syncfusion Team September 9, 2024 01:20 PM UTC

Andreas,


Thanks for being patience. We have ensured your reported scenario by running an attached sample in debug mode. Range navigator is rendered properly without any exception. We have attached the gif for your reference.

We also request you to share the replication steps to reproduce this scenario so that it will be helpful for us to analyze further and assist you better. Please let us know if you have any concerns.


Attachment: ProgressBar_84b8a884.zip

MK Mobolaji Kuti October 1, 2024 12:52 PM UTC

Hi,

We are also having the same issue. I downloaded OP's project with the progress bar and was able to replicate the same error.


When previously using Visual Studio 17.10.x, there was no issue. Since updating to Visual Studio 17.11.x, this has been an issue.

Error: Could not find 'sfBlazor.getElementBoundsById' ('getElementBoundsById' was undefined).

  Message=

  Source=

  StackTrace:

  at https://localhost:7295/_framework/blazor.webassembly.js:1:328

    at Array.forEach (<anonymous>)

    at a.findFunction (https://localhost:7295/_framework/blazor.webassembly.js:1:296)

    at _ (https://localhost:7295/_framework/blazor.webassembly.js:1:2442)

    at https://localhost:7295/_framework/blazor.webassembly.js:1:3330

    at new Promise (<anonymous>)

    at Object.beginInvokeJSFromDotNet (https://localhost:7295/_framework/blazor.webassembly.js:1:3311)

    at Object.Gt [as invokeJSFromDotNet] (https://localhost:7295/_framework/blazor.webassembly.js:1:62569)

    at Object.Ii (https://localhost:7295/_framework/dotnet.7.0.20.hqs5bjbv9e.js:5:71974)

    at _mono_wasm_invoke_js_blazor (https://localhost:7295/_framework/dotnet.7.0.20.hqs5bjbv9e.js:14:103886)



DG Durga Gopalakrishnan Syncfusion Team October 2, 2024 11:22 AM UTC

Hi Mobolaji,


We have ensured the reported scenario in latest version with attached sample; progress bar is rendered properly without any console exception. We have attached the GIF for your reference.


GIF : https://www.syncfusion.com/downloads/support/directtrac/general/ze/ProgressBarRender1742022559.zip


We request you to share the below information which will be helpful to validate this case further.

  • Please share the replication steps or video.
  • Share if you have done any other customization.
  • Browser used.
  • Default system configuration.
  • Locale used.


Please let us know if you have any other concerns.


Regards,

Durga Gopalakrishnan.



ÁN Ángel November 6, 2024 08:07 PM UTC

Same Issue here,

Since updated VS2022 to version 17.11.5, same exception occurs on sf progressbar. As Andreas stated when you click 'continue' it continues working without problem but error happens.


Image_3447_1730923513925






DG Durga Gopalakrishnan Syncfusion Team November 7, 2024 11:04 AM UTC

Angel,


The reported problem commonly occurs in older .NET version WebAssembly applications with certain configurations related to debugging in Visual Studio. To resolve this, we recommend including the script below in your application. A modified sample is attached for your reference.


<head>

    <script src="https://cdn.syncfusion.com/blazor/syncfusion-blazor-base.min.js"></script>

</head>


Sample : https://www.syncfusion.com/downloads/support/directtrac/general/ze/BlazorSFProgressbar1108138462.zip


If you are still facing problem, please try to replicate the problem in above sample or share any other configuration done in VS, so that it will be helpful to validate this case further. Kindly revert us if you have any concerns.


ÁN Ángel November 8, 2024 08:02 PM UTC

Hello,

I added the line as you said, but error still happens, Im Using syncfusion blazor version 24.1.41

This is the 'head' part of the index html code:

<head>

    <meta charset="utf-8" />

    <title>Gates</title>

    <base rel='nofollow' href="/" />

    <link rel='nofollow' href="css/app.css" rel="stylesheet" />

    <link rel='nofollow' href="manifest.json" rel="manifest" />

    <link rel='nofollow' href="https://cdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-1BmE4kWBq78iYhFldvKuhfTAU6auU8tT94WrHftjDbrCEXSU1oBoqyl2QvZ6jIW3" crossorigin="anonymous">

    <link rel='nofollow' href="_content/Syncfusion.Blazor.Themes/bootstrap5.css" rel="stylesheet" />

    <script src="https://cdn.syncfusion.com/blazor/24.1.41/syncfusion-blazor.min.js" type="text/javascript"></script>

    <script src="https://cdn.syncfusion.com/blazor/syncfusion-blazor-base.min.js"></script>

</head>


I just downloaded your sample and same error happens on the sample project you provided:

Image_1389_1731096039278


And yes I'm using .net version 7, this is an old project and upgrading it to .net 8 could bring more trouble than benefit.

Please let me know your suggestions.


Regards!,



DG Durga Gopalakrishnan Syncfusion Team November 11, 2024 02:51 PM UTC

We are validating your reported scenario. We will update the further details within two business days. We appreciate your patience until then.


DG Durga Gopalakrishnan Syncfusion Team November 12, 2024 06:05 AM UTC

Angel,


We have checked the reported scenario with multiple devices. We were able to replicate the reported problem. So, we have considered this case as bug and logged a defect report for the issue ”Exception while running progress bar application”. This fix will be available in our weekly patch release which is scheduled to be rolled out on 19th November 2024. We appreciate your patience until then. You can keep track of the bug from the below feedback link.


Feedback : https://www.syncfusion.com/feedback/62997/exception-while-running-progress-bar-application


If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal.


Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”


DG Durga Gopalakrishnan Syncfusion Team November 25, 2024 02:31 PM UTC

Angel,


We are glad to announce that our v27.2.3 patch release is rolled out; we have added the fix for reported issue. You can use the latest Syncfusion.Blazor.Charts NuGet package.


Root Cause:

The method invoked on the script to calculate the element size for the progress bar was improper, which throws an exception.


Fix:

Provided the appropriate invoking methods to calculate the element bounds for the progress bar.


NuGet Package : https://www.nuget.org/packages/Syncfusion.Blazor.Charts/


Sample : https://www.syncfusion.com/downloads/support/directtrac/general/ze/BlazorSFProgressbar-1077725651.zip


Feedback : https://www.syncfusion.com/feedback/62997/exception-while-running-progress-bar-application


We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.


Marked as answer
TG Tom-Brian Garcia replied to Durga Gopalakrishnan January 30, 2025 05:52 PM UTC

Did you only patch Syncfusion.Blazor.Charts or also other packages ? I tried updating all my packages to 28.2.3 and I still get the exact same issue


My packages :

Syncfusion.Blazor
Syncfusion.Blazor.Cards
Syncfusion.Blazor.Grids
Syncfusion.Blazor.ProgressBar
Syncfusion.Blazor.SfPdfViewer


Thanks in advance !


DG Durga Gopalakrishnan Syncfusion Team February 3, 2025 09:49 AM UTC

Thank you for reaching out to us.


We are happy to inform you that the reported issue has been resolved, and the fix is now included in the latest version of the Syncfusion.Blazor.ProgressBar package. To resolve the issue on your end, please update to the latest version available. We have thoroughly tested your scenario by upgrading the project to version 28.2.3, and we can confirm that the progress bar is now rendering correctly without any exceptions. For your reference, we have attached the tested sample and a screenshot.



To ensure a smooth experience after updating, we kindly recommend clearing both your NuGet cache and browser cache before running the application again.


If you continue to experience any difficulties, please don’t hesitate to share the following information, which will help us investigate the issue further and provide you with a prompt resolution:


  • Try replicating the issue using the attached sample.
  • Share your sample or relevant code snippet, including full configuration details.
  • Provide a detailed description of the issue replication steps or a video.
  • Let us know if you have made any other customizations.



We appreciate your patience and are here to assist you further if needed.


Attachment: BlazorSFProgressbar_f8fc2540.zip

TG Tom-Brian Garcia replied to Durga Gopalakrishnan February 10, 2025 05:44 PM UTC

Thanks a lot  for your quick reply and fix, that's some really impressive reactivity !

No more errors using  Syncfusion.Blazor.ProgressBar version 28.2.3


(however I updated from a version old of many months, I had to remove height/width parameters from my Circle progress bar, or else it was really small until a screen resize, but not big deal)


DG Durga Gopalakrishnan Syncfusion Team February 11, 2025 09:41 AM UTC

Tom,


You're most welcome!


By default, when the height and width are specified in percentage, the size adjusts dynamically based on the window size. For example, if the height and width are set to 50%, the progress bar will occupy 50% of the available window size, adapting as the window resizes.


However, when specified in pixels, the size remains fixed, regardless of window resizing. This is the expected behavior.


Please let us know if you have any concerns.


Loader.
Up arrow icon