mynotification | custom notification on Windows

You're using a UITabBarController to host the views. The system initially only loads the view controller it needs to display (ViewController in this case). Then, once you click on the tab for the SecondVC, it loads that view controller.

You can verify this by putting a print statement in viewDidLoad of SecondVC.

You can also verify that if you navigate to SecondVC before going back to ViewController and pressing Notify, both view controllers get notified in this scenario.

So, it's not a bug -- it's just an implementation detail of when the views are loaded.

If you want to find a way to make sure that SecondVC has access to that information when it's loaded, you have two options:

1. Rely on a different system of propagating the state
2. Put your notification listener in required init?(coder: NSCoder) instead of viewDidLoad (this does get called during setup). This has a caveat though: the UILabel won't be loaded yet, so you'd have to store that state for loading later. Trying to access mySecondLabel before viewDidLoad will result in a crash.

Update Updated code that stores the Notification in the event that you want to use the init method:

That's trivial. Just update the state of "isLogged" on the "Menu" page after you login.

i found the problem:

From the FCM you need to send a message to a device id, or subscribe a user to a certain topic. You need to send to a topic or group or certain device token.

You cannot just send messages to a device if you don't have the three. It won't work. Follow the following

Follow this link to know how to fully send a message with FCM

You have this in your MyFeed component:

You cannot receive the notification at the same level of where it was dispatched. Please refer to docs : https://api.flutter.dev/flutter/widgets/NotificationListener-class.html

NotificationListener class : A widget that listens for Notifications bubbling up the tree.

I've updated your code to make it work.

TL;DR:

Most likely, jsonfield package is not incompatible with Django==1.11.18

Details:

You are using Django in version 1.11.18, which requires 5 positional arguments for from_db_value method and do not support JSONFields.

You are also using django-notifications package, which internally uses jsonfield>=1.0.3 package. Since there is no max. version set, django-notifications uses the newest version of jsonfield package.

The newest versions of jsonfield (3.0.0 and higher) doesn't support Django below 2.2. One of the reasons is that it takes only 4 arguments instead of 5.

The highest version of jsonfield that supports Django 1.11 is jsonfield==2.1.1

Please check the version of installed jsonfield package (use grep only if you're on unix sytem):

I found the answer here in this link:

I add the key by using the below line:

You are not making a correct request, it also seems that your URL is not pointing towards a database but a project instead. Firebase database storage URL's also generally look something like this: https://databaseName.firebaseio.com. This means you should setup a database in your firebase project and then use that URL in order to make requests.

I suggest also reading more about how the firebase database works in the documentation: https://firebase.google.com/docs/database.