Currently manual serialization is being used in the sdk which is not an optimal solution. So we need to migrate to Automatic JSON Serialzation using Json_serializable package

Node.js 8 has been deprecated and from 15th March 2021 onwards Node.js 8 functions will not be executed by firebase. Upgrade to Node version 10

Is your feature request related to a problem? Please describe.
Even if the expenses with a friend are settled-up, the friend is still listed on the HomePage. This makes scrolling and searching for a particular name, very difficult moreover it makes UI very congested.

Describe the solution you'd like
A separate section should be there at the end of the list with the settled-up friends.

[Please first describe the approach you are thinking before moving on with the coding part]

Describe the bug
When we cancel the google sign-in method this error is generated.

Expected behavior
Instead of showing a snack bar with an error, the method should abort without notifying the user. Like without showing any snack bars.

App gets stuck on CircularProgressIndicator whenever internet connection is unavailable. When we try to update, delete or add any expense on the app, the app gets stuck on the CircularProgressIndicator and it doesn't show any Network Error.
So, the users will not know that there is a network problem.

Add Multi Language Support

• Spanish (es)
• French (fra)
• German (de)
• Arabic (are)

Describe the bug
The new showDialog function API shows dialog with a context that isn't related to a previous context. The Bloc thus, doesn't have the required context to add an event.

Describe the bug
The input formatter that adds country dial code to the phoneNumber behaves in an absurd manner. It adds the code when someone tries to type and if the phoneNumber is picked from the phone book then it is not formatted automatically

Expected behavior
The input formatted should work automatically when input is present irrespective of whether the phone number is entered manually or via the phone book

• Validator for phone numbers without country codes
• password validator

Describe the bug
The drawer menu opens with a jag and the frame rate is slow in some devices

To Reproduce
Steps to reproduce the behavior:

1. Click on the drawer menu button or swipe right
2. See the jagging

Expected behavior
Drawer menu should open flawlessly without any delay in frames.

Describe the bug
Bad State: No Element error in Add Expense Page

To Reproduce
Steps to reproduce the behavior:

1. Go to Add Expense Page'
2. Select the Add Friend option from the dropdown menu
3. The Add New Friend Dialog appears, click on CANCEL
4. Now add the expense
5. See the error

Expected behavior
The expense should not be added when the friend is not added or precisely when the value of dropdown is "Add Friend".

Is your feature request related to a problem? Please describe.
The friend's list is not sorted. Even if the expenses are settled up the user is still displayed. This makes searching for a particular friend very difficult.

Describe the solution you'd like
Sort the friend's list in ascending order of the corresponding first name.

Describe the bug
An image should be displayed in the notes page when the notes list is empty

To Reproduce
Steps to reproduce the behavior:

1. Go to Notes Page

Describe the bug
The bad state no element occurs in the all-expenses page due to some odd expense addition from the previous bug.

How to Proceed
Add null safety in the all-expenses BLOC

Is your feature request related to a problem? Please describe.
The splash screen currently doesn't change according to the app theme. It is always light-themed.

Describe the solution you'd like
The splash screen should change according to the theme of the app

The current code for FCM (Firebase Cloud Messaging) generates a huge amount of errors. Ideally, these are the exit cases that need to be addressed. Example: When the user is logged out, the token is also erased from the database but the cloud functions do not address this case and generate an error.

We need to make the code more robust and consider all exit cases.

Describe the solution you'd like
On the details page instead of the profile menu button there should be a popup-menu button with a "delete friend" option. Clicking on the "delete friend" will settle up all expenses and delete the user from the current user's friend list. Also, the current user will be deleted from the unfriended user's friend list.
More options for the pop-menu button will be decided later.

A single call to the server should be made for a single transaction.

Transactionizing the read and write requests would overcome the problem of atomic read and writes.
In simple words, if two requests are made simultaneously to a document then either they give an error or produce some absurd result. Transactioizing them would mean that even if the requests are made at the same time, they will function correctly as several bank transactions occur simultaneously around the globe.