TastyToast | intuitive alternative to android 's system-wide toasts | Notification library

But when I am inserting more than one views in recyclerview. Changing of any rows EditText's value except the current inserted views calling the listener itself again and again.

Well, the main issue of listener replication over and over again, that theses listeners exist in onBindViewHolder() as this method gets called every time a RecyclerView row is going to be displayed/recycled/changed/inserted on the screen; and that apparently happened whenever you added new items.

So, the possible way is to register these listeners somewhere else that going to be called once, or whenever you want to; i.e. not every time the rows are recycled.

You can do that in the ViewHolder constructor to the EditText's themselves.

Challenge: how can we know which EditText that the user modified? .. As if some EditText is modified and you recycled the views (i.e. scrolled up/down the list), you will see the value is messed up in multiple rows.

This can be solved by:

• Tracking the EditText values in your model class ModelSale.. Not sure if you already did that or not.. anyways this class should have fields, getters, & setters correspond to the EditTexts fields which we have (quantity, discount, & price). And these fields should be set in the onBindViewHoder() to get the saved values whenever the rows are recycled.

It errors because the Activity is not yet created.

Moving the ViewModel instantiation to onActivityCreated lifecycle is the key

Instead of Design support library, You can use : implementation 'com.google.android.material:material:1.0.0'

Do check for the current stable version

So what I understand is you are selecting state from Spinner and getting name of state but you want to get stateId.

one possible solution, I can think of is to use HashMap map. when you receive state name from spinner just call map.get(name) and you will get state Id.

Edit:

you can implement it like this

It is throwing error after

In your ApiService

I suggest using a boolean variabale inside isUserExists method, we can update that variable inside onComplete method and rely on it to throw or not UserExistsException.

Asynctask is a Thread, which only executes the tasks which it should and doesn't need a Looper and though there is no Looper called for this Thread. The Locationlistener works different, than that, what you have tried. OnLocationchanged get's called as long as you don't stop the listener, but this is happening asynchronously and you can't just wait inside an asynctask for this to finish. You have to start the locationlistener from your Mainthread and whenever your Location gets changed the function onLocationChanged gets called. You could for example put your onPostExecution inside the locationlistener.