ExpenseManager | Android app to manage expenses | Android library

You are attempting to access the user in ExpenseManagerDbContext which is the application’s IdentityDbContext. As such, it itself is a dependency of the authentication system and will get resolved when the framework performs the authentication.

So the flow is somewhat like this:

1. Request comes in.
2. Authentication middleware runs to authenticate the user.
3. UserManager resolves ExpenseManagerDbContext.
4. ExpenseManagerDbContext resolves IGetClaimsProvider.
5. GetClaimsProvider resolves the HttpContext and attempts to access the user’s claims.
6. Authentication middleware performs the authentication and sets HttpContext.User with the result.

If you look at steps 5 and 6, you will see that the HttpContext is accessed before the authentication middleware is able to actually authenticate the user and update the user object on the context. And since the authentication middleware always runs at the beginning of a request, this will always be the case.

I would recommend you to rethink your ExpenseManagerDbContext since it probably shouldn’t depend on the currently signed-in user. It should be independent of that. If you have logic there that depends on the user id, then it should probably be a separate service.

The problem is you are using the same expense object every time.

Think of it like this, You have 1 Expense Bucket, you fill it up, and you place it in the list, then next time you use the same buck it and fill it up and add it to your list.

Now when you print out your report, you get the same value all the time (the last value). That's because you are using the same bucket!

The fix is create a new Expense Object

According to the stacktrace, it indicates that your Fragment is not visible and the callbacks are still being received.

While receiving progress callbacks you can check if your ProgressBar is not null and then only update the ProgressBar or remove the callback and cancel task when your Fragment is removed from Activity i.e; in onDestroyView() method. If and only If your task is Fragment specific.

Else you can go for AsyncTaskLoader and download data it will run in background until your operation is completed.

Thanks

The problem is because of object reuse. the object is already created so we should set the new value. if you didn't set it will show the old values.

You did correctly in Group view, but in child view, you did wrong. Set the value all the time, then it will work fine

Try this,

the tables were not getting created properly thats why data was not getting saved into the pdf.

The problem is that you have created an ExpenseTag Model but didn't add it to the Expense model as a field. I have updated the Expense model for you.

You are doing wrong over here