user.activity | Raising awareness of what you can do with a smartphones

Use this code:

The problem with your code is you are returning super.getView(position, convertView, parent) from getView while you should be returning the View you just created that is convertView . For super constructor call you have to use super(context, resource, countryList) so that Adapter can return the size of list.

Change getView like below

The problem is : .hide(400 it take 400ms to remove the item but your if condition doesn't wait this time so it works but it didn't count the removed item

To avoid that.. Use the if condition inside the hide(400 , function(){ remove , if condition}) or Change 400 to 0 it should work too

In the next code I define a function at first called ToggleShowHideEmpty then I run it in hide callback

You are correct - Cloud Functions always run after the event occurs that triggers them. This behavior can't be changed. You can't make the creation of a user successful only if your function is successful.

What you can do instead is set up a database listener at the location in the database that's expected to be written after the function complete. Your code should have the UID of the newly created user, and you can use that to build the location to query that should be populated after the function completes. Your listener will trigger when the data first becomes available, and your app can continue from there.

This is very similar to what I recommend in my article about offloading work to Cloud Functions, except my example uses Firestore.

SELECT (`booker_id`, `booking_id`) … returns one column of the ROW data type in H2 (and MySQL doesn't support such construction at all). It looks like you added these parentheses accidentally and your query should be SELECT `booker_id`, `booking_id` … without them.

Ok I found the solution I am posting it here so that other can benefit from it. All I had to do was.