Null check operator used on a null value. Error thrown null.

[alex-sandri]

Describe the bug
A null check operator error is thrown and I am not able to understand how this can be reproduced.

To Reproduce
I could not reproduce this issue.

Smartphone (please complete the following information):

• Device: OnePlus6T
• OS: Android 11

Additional context
Crashlytics report:

Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Null check operator used on a null value. Error thrown null.
       at State.context(framework.dart:942)
       at _OverlayBuilderState.addToOverlay(layout_overlays.dart:172)
       at _OverlayBuilderState.showOverlay(layout_overlays.dart:164)
       at _OverlayBuilderState.initState.<fn>(layout_overlays.dart:129)
       at SchedulerBinding._invokeFrameCallback(binding.dart:1175)
       at SchedulerBinding.handleDrawFrame(binding.dart:1113)
       at SchedulerBinding._handleDrawFrame(binding.dart:1015)

[ujas-m-simformsolutions]

@alex-sandri Can this screen be directly opened from something like notification or a deep link?

[alex-sandri]

@ujas-m-simformsolutions Yes, this screen can be opened from a notification but I don't think this was the case as that would have caused another navigation event in the app that I don't see from the Firebase Analytics logs.

[ujas-m-simformsolutions]

From looks of it, I think you are starting the showcase in the initState where it is not guaranteed to have access to the context. If this is case then use addPostFrameCallback function to skip a frame so that you have access to the context

[alex-sandri]

@ujas-m-simformsolutions Unfortunately this is not the case as all startShowCase() calls happen well after the app has initialized and all the UI has been rendered. If it may help you I can put together a minimal app sample using the same logic but with unnecessary stuff removed.

[ujas-m-simformsolutions]

@alex-sandri Yes please share minimal reproducible code.

[alex-sandri]

@ujas-m-simformsolutions I'm so sorry it took so long for me to get back to you but I've been busy and so I couldn't put together a minimal app sample for you to test with. I just noticed a new issue (#313) and that seems to be related to this one and it already has a fix. So I'm closing this for now and will reopen in the future if the problem persists.