Foundation | Type your boilerplate code

The issue with default guard. So it should be web

Your problem is that you have set SESSION_CONNECTION=session, but your SESSION_DRIVER=default, so you have to use SESSION_DRIVER=database in your .env. See the config/session.php:

Your page is not re built after logging in the user, that is why your nav bar is not updated. When you click on the button it refreshes and correctly displays the new elements.

Instead of using a global variable you could look into a state management package in order to make the logged-in user available throughout your app. (article for getx the simplest one out there)

If this is simply a prototype and you want some quick and dirty, I guess you could trigger a reload of your app once a user logs in by wrapping your app with a widget that exposes a rebuild method. (article)

EDIT: Example with Getx:

What's happening here is a pretty subtle behavior.

The expression x.$data evaluates to a Published.Publisher. When you subscribe to a Published.Publisher, it publishes its current value immediately, and then each time the Published property receives a new value, the publisher publishes the new value before the new value is stored in the property.

This behavior is documented in the Published reference:

When the property changes, publishing occurs in the property’s willSet block, meaning subscribers receive the new value before it’s actually set on the property.

This means when you call x.setData(), the outer subscription receives the new value ("DATA") in v1, but x.data at that point still evaluates to nil. And when you create the inner subscription to x.$data, it immediately publishes its currently stored value, which is still nil.

As mentioned by @oguz_ismail in the comments, bug-bash@gnu.org is the appropriate place to report the bug.

However, a certain format for the email is required/requested, when you need to report a bug.

All bug reports should include:

• The version number of Bash.
• The hardware and operating system.
• The compiler used to compile Bash.
• A description of the bug behaviour.
• A short script or ‘recipe’ which exercises the bug and may be used to reproduce it.

You can find ALL the details at: https://www.gnu.org/software/bash/manual/html_node/Reporting-Bugs.html

Finally, there is a helper script built into bash itself. Call bashbug from the command line, and it will populate most of the requirements, leaving you to fill out the description and the steps required to reproduce the bug.

I just Found a Solution to this problem! Basically the FireFlutter Team had fixed a production level bug and inturn that exposed a flaw of the Dart SDK. As this was only a Development only bug (bug only during Hot Restart), it was not given importance.

In my Research I have found that the last version combination that supports StreamBuilder and Hot Restart is

firebase_auth: 0.20.1; firebase_core 0.7.0

firebase_auth: 1.1.0; firebase_core: 1.0.3

These are the only versions that It works properly on. Every subsequent version has the new upgrade that has exposed the bug.

The Solution is very Simple! Works for the latest version (1.2.0) of the firebase_auth and firebase_core plugins too!

Firstly Import Sharedpreferences

The problem is that your publisher is too artificially crude: it is not asynchronous. An array publisher just publishes all its values at once, so you are canceling too late; and you are blocking the main thread. Use something like a timer publisher instead, or use a flatmap with a delay and backpressure.

It doesn't appear that they've documented how you can do this, but it looks possible from the Fortify config file.

Open config/fortify.php and comment or remove Features::registration(), from the array:

When we use Lambda we need to write our code inside the lambda_handler method
"def lambda_handler(event, context):" .

As you mentioned you are using lambda to run this code then probably the below code should work for you.