SwipeLayout | android swipe gesture detector layout | Android library

A TitleView Sounds like the best option for what you're trying to do. Instead of those long processes you could just do this

The error is telling you that the object reference webSite is null. You need to check the process that is calling the ListSourceAdapter constructor to see what is causing it to send null to the constructor call.

According to your code and description, you can try add one LinearLayout in SwipeRefreshLayout, then adding child element in LinearLayout, like this:

Learning Xamarin and I am trying to scroll my Frame Layour down and reveal a search bar for my list view. Here is what is happening:

I use your code to test, but I have no problem when translating by Y in SwipeRefreshLayout__Refresh event.

Replacing all the mapbox dependencies with this solved my problem :

This is not a good practice to make API calls in adapter. You can create callbacks from adapter to activity and should call this API code in activity itself. If you need some references from the adapter then you can create methods in adapter and call these methods in activity by creating adapter's object.

To get response/data back from adapter to activity, you'll need to implement callback pattern like below example:

RecyclerView Adapter sudo code:

There are many potential solutions here that I can think of. However, given the app needs to have predictable and reasonable user experience, herein I'm scoping out the issues first.

• Since a random resource is being requested each time, there's always a chance of it being null. Hence, multiple round-trips cannot be done away with (but can be reduced).
• Multiple HTTP round-trips, that too with the unpredictability of returning null several times, can be really frustrating user experience.

Below are the potential ways (in increasing order of complexity) this can be dealt with.

1. The simplest solution is to implement logic on the repository level, wherein the function getCuriosityPhotos is responsible to request the api resource indefinitely till it responds with a not null data. This will solve the core issue that the user will eventually be shown something (but it might take a hell lot of time).

(PS- You'll also need to delegate the random number generation as a potential service available to the repository.)

1. To reduce the number of requests and hence wait-time for the user, you can save to the in-app database, the request params as well as the response. Thus, your database can act as a single source of truth. Hence, before making a request, you can query the database to check if the app had previously requested the same params earlier. If it did not, dispatch the request else if it did, then there's no need to request again and you can use the previous result. If it was null, regenerate another random number and try again. If it was not null, serve the data from the database. (This is a good enough solution and as more and more requests & responses are saved, user wait time would continually reduce)

(Note: In case the endpoints do not respond with static data and the data keeps changing, prefer using an in-memory database than a persistent database such as SQLite)

1. The app can run a background service that continually (by iterating over all possible combinations of the request params) requests and saves the data into the database. When the user requests random data, the app should display a random set of data from within the database. If the database is empty/does not meet a threshold of having at least n number of rows in the database, the app can perhaps show an initialization setup UI.

Pro-tip: Ideally (and in case you are building a product/service), mobile apps are meant to be very very predictable and have to be mindful of a user's time. Hence, the very task of requesting data from such resources should be a task of a backend server and database which operate some sort of service to fetch and store data and in-turn the app would request this server to fetch data amongst this subset which does not have any null values.

I've answered this question from a perspective of solving the problem with varying granularity. In case you need help/advice on the technical implementation part, let me know, I'll be happy to help!

put your refersh logic in onResume() instead of onCreate(), it's an issue of lifecycle management.