Closed aliemrenebiler closed 2 years ago
Hi @aliemrenebiler,
We have checked with the latest version of Flutter SDK and the reported scenario was reproduced at our end. We have ensured the user interactions and other cases with circular charts and chart was working fine as expected. Since the scenario was replicated and we are not aware of your exact scenario, we request you to provide the following information, • what are properties have you used for the chart widget in your project. • The exact scenarios in which the issue got replicated i.e changing the orientation of the device while showing the tooltip, etc. These are more helpful to us to provide a solution sooner. We have also attached a sample for your reference which is used in the testing phase, if possible, kindly try to replicate it with this sample and revert us.
Sample: i372926.zip
Thanks, Yuvaraj.
Hi @Yuvaraj-Gajaraj
This error just shows up at the beginning. But the app can still be used. During usage, no such error appears again. I made the app for Linux, used syncfusion_flutter_charts: ^19.4.56
as the package.
I didn't have this problem before the last Flutter update.
I copied the chart codes so you can investigate.
chart_code_1.txt chart_code_2.txt chart_code_3.txt chart_code_4.txt chart_code_5.txt
@Yuvaraj-Gajaraj is there any update about this problem? I still have the same problem
I was able to replicate this same error using the Syncfusion Chart Example without any other modifications.
These are warning messages we get from Flutter 3 since SchedulerBinding.instance no longer returns a nullable value.
As a reference, flutter_slidable had the same warning until yesterday's release when they added the following fix. Note that the lint instruction "// ignore: unnecessary_nullable_for_final_variable_declarations" is required to clear lint warnings on your development environment.
Fix supporting Flutter 3 and Flutter 2: // In Flutter 3, [SchedulerBinding.instance] is not nullable, but since // we want to support Flutter 2, this is a simple way to do it without // having a build warning. // ignore: unnecessary_nullable_for_final_variable_declarations final SchedulerBinding? schedulerBinding = SchedulerBinding.instance;
Then use this local schedulerBinding where you used to access SchedulerBinding.instance, keeping ! or ? operands.
-- Ricardo
Yes! Last update was fixed everything.
This last update of Flutter has some changes about null values.
I have this error for circular_base.dart file and many more files in syncfusion_flutter_charts package: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.
The warnings are always about the same code lines:
They want it as 'instance', not 'instance!' or 'instance?'.