reactiveui/fusillade

An opinionated HTTP library for Mobile Development

What is ReactiveUI?

ReactiveUI is a composable, cross-platform model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming, which is a paradigm that allows you to abstract mutable state away from your user interfaces and express the idea around a feature in one readable place and improve the testability of your application.

🔨 Get Started 🛍 Install Packages 🎞 Watch Videos 🎓 View Samples 🎤 Discuss ReactiveUI

Book

There has been an excellent book written by our Alumni maintainer Kent Boogart.

NuGet Packages

Install the following packages to start building your own ReactiveUI app. Note: some of the platform-specific packages are required. This means your app won't perform as expected until you install the packages properly. See the Installation docs page for more info.

Platform	ReactiveUI Package	NuGet
.NET Standard	ReactiveUI
	ReactiveUI.Fody
Unit Testing	ReactiveUI.Testing
WPF	ReactiveUI.WPF
UWP	ReactiveUI.Uwp
WinUI	ReactiveUI.WinUI
MAUI	ReactiveUI.Maui
Windows Forms	ReactiveUI.WinForms
Xamarin.Forms	ReactiveUI.XamForms
Xamarin.Essentials	ReactiveUI
AndroidX (Xamarin)	ReactiveUI.AndroidX
Xamarin.Android	ReactiveUI.AndroidSupport
Xamarin.iOS	ReactiveUI
Xamarin.Mac	ReactiveUI
Tizen	ReactiveUI
Blazor	ReactiveUI.Blazor
Platform Uno	ReactiveUI.Uno
Platform Uno	ReactiveUI.Uno.WinUI
Avalonia	Avalonia.ReactiveUI
Any	ReactiveUI.Validation

Sponsorship

The core team members, ReactiveUI contributors and contributors in the ecosystem do this open-source work in their free time. If you use ReactiveUI, a serious task, and you'd like us to invest more time on it, please donate. This project increases your income/productivity too. It makes development and applications faster and it reduces the required bandwidth.

Become a sponsor.

This is how we use the donations:

• Allow the core team to work on ReactiveUI
• Thank contributors if they invested a large amount of time in contributing
• Support projects in the ecosystem

Support

If you have a question, please see if any discussions in our GitHub issues or Stack Overflow have already answered it.

If you want to discuss something or just need help, here is our Slack room, where there are always individuals looking to help out!

Please do not open GitHub issues for support requests.

Contribute

ReactiveUI is developed under an OSI-approved open source license, making it freely usable and distributable, even for commercial use.

If you want to submit pull requests please first open a GitHub issue to discuss. We are first time PR contributors friendly.

See Contribution Guidelines for further information how to contribute changes.

Core Team

Glenn Watson Melbourne, Australia	Chris Pulman United Kingdom	Rodney Littles II Texas, USA
Colt Bauman South Korea	Artyom Gorchakov Moscow, Russia

Alumni Core Team

The following have been core team members in the past.

Geoffrey Huntley Sydney, Australia	Kent Boogaart Brisbane, Australia	Olly Levett London, United Kingdom
Anaïs Betts San Francisco, USA	Brendan Forster Melbourne, Australia	Claire Novotny New York, USA

.NET Foundation

ReactiveUI is part of the .NET Foundation. Other projects that are associated with the foundation include the Microsoft .NET Compiler Platform ("Roslyn") as well as the Microsoft ASP.NET family of projects, Microsoft .NET Core & Xamarin Forms.

fusillade's Issues

POST requests are being de-duplicated

Spurious POST requests are being de-duplicated. For me, this meant that only some data was being submitted to the server, and the rest was being silently dropped :(

I worked around this by sticking this at the start of RateLimitedHttpMessageHandler.SendAsync:

            if (request.Method == HttpMethod.Post)
            {
                return base.SendAsync(request, cancellationToken);
            }

I believe other methods should also be excluded from de-duplicating, such as PUT. If we can agree here on what methods should be excluded, and whether the above approach is fine, I'm happy to submit a PR.

Image request in Fusillade

I am trying to the "Auto-deduplication of requests" feature on Fusillade. I try to fetch a same image 10 times. And it is sending 10 requests to the server. The url is same for all requests. Am I doing something wrong?

Here is the sample test code:

 Uri u =  new Uri("http://www.brandeis.edu/about/images/newformat/map2.jpg");
 for (int i = 0; i < 10; i++)
  {
                HttpClient hc = new HttpClient(NetCache.UserInitiated);
                var s = await hc.GetAsync(u);

                var st = await s.Content.ReadAsStreamAsync();
}

Add package issues with Rx-Main

Hi,

I would like to use Fusillade into a PCL Xamarin Forms project, but I failed to add the package. It seems there's an issue with RX-Main dependency. Here is what the message I get into the console :

Could not install package 'Rx-Interfaces 2.2.4'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile259'

OK, so I guess it's just that Rx-Main (and its dependencies) doesn't support PCL Profile259 at all (which is weird because when I open the package, there's the right folder in the lib directory).

When I get that kind of error, I always search the package page on Nuget to look at the supported platforms, which I did. But this time, it looks like Rx-Main is not on Nuget anymore and has been unpublished by MS :

https://www.nuget.org/packages/rx-main

It says :

"The owner has unlisted this package. This could mean that the package is deprecated or shouldn't be used anymore."

Could you please update Rx-Main dependency with their new library for Reactive ?
https://www.nuget.org/packages/System.Reactive/

It supports net-standard 1.0 and should be usable once I migrate my PCL project to .Net Standard.

Many Thanks !

[BUG] Crashing on iOS when aeroplane mode enabled.

Describe the bug

When using Fusilade as a httpmessagehandler in an iOS app via

var httpHandler = new Fusillade.RateLimitedHttpMessageHandler(
                            new NSUrlSessionHandler(),
                            Fusillade.Priority.Background);
                        var httpClient = new System.Net.Http.HttpClient(httpHandler)
                        {
                            BaseAddress = uri
                        };

the app will crash when wifi and cellular is disabled(no data).

Steps To Reproduce

Expected behavior

App should work without crashing even if it does not have internet access.

Screenshots

Environment

• OS: iOS 12.4.8
• Device: iPhone 6
• Version: 2.2.9
• Working Version: None that I know of?

Additional context

Crash stack trace:

error	15:07:29.424320+1000	Life	Task <B0D7871B-099F-4E4E-A62C-57BB7A36EC01>.<1> finished with error [-1009] Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo={_kCFStreamErrorCodeKey=50, NSUnderlyingError=0x2837c0030 {Error Domain=kCFErrorDomainCFNetwork Code=-1009 UserInfo={_kCFStreamErrorCodeKey=50, _kCFStreamErrorDomainKey=1}}, _NSURLErrorFailingURLSessionTaskErrorKey=<private>, _NSURLErrorRelatedURLSessionTaskErrorKey=<private>, NSLocalizedDescription=The Internet connection appears to be offline., NSErrorFailingURLStringKey=<private>, NSErrorFailingURLKey=<private>, _kCFStreamErrorDomainKey=1}
default	15:07:29.428785+1000	Life	Execution aborted in method: <<SendAsync>b__2>d::MoveNext
default	15:07:29.428833+1000	Life	Line=6471 IP=0x6623a21, Aborted execution
default	15:07:29.428864+1000	Life	0x6623a21 26f
default	15:07:29.428900+1000	Life	error: * Assertion: should not be reached at /Users/builder/jenkins/workspace/archive-mono/2020-02/ios/release/mono/mini/interp/interp.c:508

Update NuGet packages to reflect resolutions to issue14 & PR 15

Can the Nuget packages be updated to included the latest updates? This caused me issues with the enqueued failing requests with the RateLimitedHttpMessageHandler class.

CancellationToken hangs all subsequent requests

First off, thanks for the repo. Great work.

I have run across what I believe to be a fairly serious bug. Anytime Cancel is called on a CancellationTokenSouce all subsequent requests hang. I have created a simple test case that exhibits this: https://gist.github.com/cbrammer/0505f733422c60ddc6fbd9755e62b70b

1. Could you verify that this is actually a bug and not something that I am overlooking?
2. Fix it please :)

What do the priorities mean?

I see the following priorities defined in the library but not all of them are spelled out in the read me. Could someone please shed some light on what each means and when to use them? Explicit is never mentioned at all.

public enum Priority
  {
    Explicit = 0,
    Speculative = 10,
    Background = 20,
    UserInitiated = 100,
  }

Reduce dependencies on newer TFM

Describe the problem you are trying to solve.
I do not want System.Net.Http listed as a dependency for net 6+.

Available workarounds
Accept un-necessary dependency

Additional context
N/a

Error MT2002: Failed to resolve assembly: 'Fusillade, Version=0.7.0.0, Culture=neutral, PublicKeyToken=null' (MT2002)

I added fusillade to a PCL project via nuget. Project explorer shows no error. But when I run the iOS project which references the PCL, I'm getting this error:

Error MT2002: Failed to resolve assembly: 'Fusillade, Version=0.7.0.0, Culture=neutral, PublicKeyToken=null' (MT2002)

Android project which references the same PCL runs fine.

All async methods should use ConfigureAwait(false)

https://reactivex.slack.com/archives/C03A78APB/p1490331187048801

https://reactivex.slack.com/archives/C03A78APB/p1490409996693112

Adding separate reference of System.Net.Http while adding Fusillade (Xamarin)

Why Fusillade is adding additional System.Net.Http And other System dependencies along with Xamarin Forms nuget package.

I believe these libraries are already available in Xamarin Forms. Is it a bug or something intentional?

Project still active?

Hey yall, first off thanks (Paul/Geoff/Martijn) for everything you guys do in the Xamarin space. Being new to Xamarin, I've heavily relied on both your online content as well as code to spin up and be productive.

I caught an older talk by Paul that mentioned this project, and being familiar w/ Volley on the Android side I figured it was worth a look. I notice that things haven't been updated in a while now so I was just wondering if you consider the project active or not. No worries if not, you don't owe me anything, I just didn't necessarily want to integrate it into my project if not : )

Thanks again!

Requests that fail cannot be retried

While testing my mobile app under bad network conditions, I noticed that if I make a request when a network connection is not available, an exception is thrown stating there is no internet connection as expected. However, if the network connection becomes available and I make the same request again the same exception is thrown no matter how many times I retry.

I think this is because the operation that gets enqueued on lines 99 - 124 in RateLimitedHttpMessageHandler.cs does not handle network exceptions that may be thrown as a result of the call on line 99. Any exceptions thrown in this operation would cause line 123 to never run and therefore the in-flight response to never be removed. When the request is retried the same unique key is generated and the previously failed response gets returned.

Circular dependency detected

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Try to install the Fusillade NuGet package into my Xamarin.Android project. Get the error: Circular dependency detected 'fusillade 1.0.0 => System.Reactive 3.1.1 => System.Reactive.PlatformServices 4.0.0 => System.Reactive 3.1.1'.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

• Create a new Xamarin.Android project.
• Install the Fusillade package from NuGet.

What is the expected behavior?

The Package installs

What is the motivation / use case for changing the behavior?

Which versions of Fusillade, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and snapshot (https://www.myget.org/feed/Fusillade/package/nuget/Fusillade) versions.

Fusillade: 1.0.0
VS4Mac: 7.5.3

Other information (e.g. stacktraces, related issues, suggestions how to fix)

Possibly updating the packages may fix the issue.

[BUG] Refit + Fusillade fails with System.ObjectDisposedException

Describe the bug
Actually the same as #34 witch is closed but not fixed.
Using Refit with Fusillade fails with System.ObjectDisposedException: Cannot access a disposed object. Object name: 'System.Net.Http.HttpConnectionResponseContent'.
The exception is thrown at Refit.RequestBuilderImplementation.d__15`1.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 324
It seems that when Fusillade deduplicates requests returning val.Response.ToTask(cancellationToken), Refit fails deserializing HttpContent because it's disposed.

As @clairernovotny on the Refit side with issue #1048 think it looks like a Fusillade bug, I opened the same issue on the Fusillade side.
I don't know if the bug comes from Refit or Fusillade, but I know it throws when using one with each other.

Steps To Reproduce
Create a Refit RestService with any Fusillade's NetCache HttpMessageHandler into the HttpClient, and send the same request at least twice at the same time.
Something dummy like:

try
{
	var reqResService = RestService.For<IReqResService>(new HttpClient(NetCache.UserInitiated)
	{
		BaseAddress = new Uri("https://reqres.in/api")
	});

	var task1 = reqResService.GetUsersAsync();
	var task2 = reqResService.GetUsersAsync();

	var result = await Task.WhenAll(task1, task2);
	var userList = result.FirstOrDefault();
}
catch (Exception e)
{
	throw;
}

with IReqResService:

public interface IReqResService
{
	[Get("/users")]
	Task<UserList> GetUsersAsync();
}

and Models:

public class UserList
{
	[JsonProperty("page")]
	public int Page { get; set; }

	[JsonProperty("per_page")]
	public int PerPage { get; set; }

	[JsonProperty("total")]
	public int Total { get; set; }

	[JsonProperty("total_pages")]
	public int TotalPages { get; set; }

	[JsonProperty("data")]
	public List<User> Data { get; set; }
}

public class User
{
	[JsonProperty("id")]
	public int Id { get; set; }

	[JsonProperty("first_name")]
	public string FirstName { get; set; }

	[JsonProperty("last_name")]
	public string LastName { get; set; }

	[JsonProperty("avatar")]
	public string Avatar { get; set; }

	[JsonProperty("email")]
	public string Email { get; set; }
}

Well interface and models are not the point, it's just to illustrate the bug.
Note that everything succeed when using Fusillade without Refit, I mean using HttpClient directly like:

try
{
	var client = new HttpClient(NetCache.UserInitiated)
	{
		BaseAddress = new Uri("https://reqres.in/api/users")
	};

	var task1 = client.GetAsync("");
	var task2 = client.GetAsync("");

	var responses = await Task.WhenAll(task1, task2);
	var jsonString = await responses.First().Content.ReadAsStringAsync().ConfigureAwait(false);
	var userList = JsonConvert.DeserializeObject<UserList>(jsonString);
}
catch (Exception e)
{
	throw;
}

Note that everything succeed to, when using Refit without Fusillade like:

try
{
	var reqResService = RestService.For<IReqResService>("https://reqres.in/api");

	var task1 = reqResService.GetUsersAsync();
	var task2 = reqResService.GetUsersAsync();

	var result = await Task.WhenAll(task1, task2);
	var userList = result.FirstOrDefault();
}
catch (Exception e)
{
	throw;
}

So it's only when using both of it.

Expected behavior
Should return result

Environment

• OS: All
• Device: All
• Version: All

[Question] Do you only use Fussillade in Get methods or do Post/Delete etc also benefit?

Hi Paul,

Small question regarding the use of Fussillade. Do you design your API client service POST/DELETE/etc methods also with a priority parameter? In other words, do you differentiate between background/user_initiated for non-GET methods?

I tend to think those non-GET methods should also be as quick as possible... so always user_initiated.

NuGet Package - Warning on every build

The DLL provided by the NuGet package generates the following warnings on every build in Xamarin Studio. I've switched over to a compiled version of the sources and no such build warning occurs.

MTOUCH:  warning MT3005: The dependency 'System.Threading.Tasks, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of the assembly 'Fusillade, Version=0.6.0.0, Culture=neutral, PublicKeyToken=null' was not found. Please review the project's references.
MTOUCH:  warning MT3006: Could not compute a complete dependency map for the project. This will result in slower build times because Xamarin.iOS can't properly detect what needs to be rebuilt (and what does not need to be rebuilt). Please review previous warnings for more details.
MTOUCH:  warning MT3005: The dependency 'System.Threading.Tasks, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of the assembly 'Fusillade, Version=0.6.0.0, Culture=neutral, PublicKeyToken=null' was not found. Please review the project's references.
MTOUCH:  warning MT3006: Could not compute a complete dependency map for the project. This will result in slower build times because Xamarin.iOS can't properly detect what needs to be rebuilt (and what does not need to be rebuilt). Please review previous warnings for more details.

A message handler for authentication

Hi Paul!

I'm currently working on a project where I authenticate every api call using OAuth2/OpenId. To use this within the Fusillade stack, I've created a message handler which will do the api request, and if the request fails because the token has expired (unauthorized response), I'll post a new request to refresh the token, and re-post the original api request.

Now I would like optimize it. Currently, some of my views are making calls to my api in a concurrent way, all with a different priority. From what I see, there are at least 3 concurrent api requests at one time. Now when the token has expired, each of those concurrent api request will fail and all of them will refresh the token. I'd like only one request to refresh the token and pass its result to the other two. After the token has been refreshed, all concurrent requests should execute again.

How would you implement such a message handler?

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency dotnet-sdk to v8.0.204
• chore(deps): update dependency roslynator.analyzers to v4.12.1
• chore(deps): update dependency verify.xunit to v24
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/ci-build.yml

.github/workflows/lock.yml

• dessant/lock-threads v5

.github/workflows/release.yml

nuget

src/Directory.build.props

• Roslynator.Analyzers 4.12.0
• stylecop.analyzers 1.2.0-beta.556
• Nerdbank.GitVersioning 3.6.133
• coverlet.msbuild 6.0.2
• PublicApiGenerator 11.1.0
• FluentAssertions 6.12.0
• Verify.Xunit 22.11.5
• Xunit.StaFact 1.1.11
• xunit.runner.visualstudio 2.5.8
• xunit.runner.console 2.7.1
• xunit 2.7.1
• Microsoft.NET.Test.Sdk 17.9.0
• Microsoft.SourceLink.GitHub 8.0.0

src/Fusillade.Tests/Fusillade.Tests.csproj

src/Fusillade/Fusillade.csproj

• System.Reactive 6.0.0
• System.Net.Http 4.3.4

src/global.json

• dotnet-sdk 8.0.101
• MSBuild.Sdk.Extras 3.0.44

---

• Check this box to trigger a request for Renovate to run again on this repository

ReactiveUI > 8.3.1 Incompatibility

Hello,

Love the project, but currently unusable with ReactiveUI 8.4.1 and greater.

Version conflict detected for System.Reactive. Reference the package directly from the project to resolve this issue.

Rfs.TracsMobile.Xamarin.Forms -> ReactiveUI.Events.XamForms 8.7.2 -> System.Reactive (>= 4.0.0)
Rfs.TracsMobile.Xamarin.Forms -> Rfs.TracsMobile.Xamarin.Core -> fusillade 1.0.0 -> System.Reactive (>= 3.1.1 && < 4.0.0).

Any suggestions or workarounds?

Thanks,

Chet

Method 'Fusillade.RateLimitedHttpMessageHandler..ctor' not found.

Note: for support questions, please ask on StackOverflow: https://stackoverflow.com/questions/tagged/Fusillade . This repository's issues are reserved for feature requests and bug reports.

Do you want to request a feature or report a bug?

bug

What is the current behavior?

I upgraded our nuget package and I am getting this error. Any ideas?

private T Background
{
get
{
return new Lazy(() => createClient(
new RateLimitedHttpMessageHandler(new NativeMessageHandler(), Priority.Background))).Value;
}
}

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Which versions of Fusillade, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and snapshot (https://www.myget.org/feed/Fusillade/package/nuget/Fusillade) versions.

Other information (e.g. stacktraces, related issues, suggestions how to fix)

System.TypeInitializationException from fusillade in win7 / VS 2015 environment

Same code breaks in Win10 /VS 2015 environment as well. On some machines (whether win 7 or 10), code wokrs fine.

Seems that similar reference issues have been earlier as well:
System.IO.FileNotFoundException: Could not load file or assembly 'Splat, Version=0.0.0.0

error.txt

UniqueKeyForRequest and POST body content

RateLimitedHttpMessageHandler:UniqueKeyForRequest doesn't take into account the content of the HttpRequestMessage when it is a POST request. POST requests which are similar and just have a different content, are considered the same request and only the first one is executed when multiple of those similar POST requests are outstanding. All calls receive the same response while they should actually receive different responses.

Xamarin.iOS Warning MT3005 - System.Threading.Tasks dependency was not found

After the Xamarin.iOS updates this week, I am receiving this compiler warning. It also manifests in weird run time crashes when the linker runs.

Full error text is below:

Warning MT3005: The dependency 'System.Threading.Tasks, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of the assembly 'Fusillade, Version=0.6.0.0, Culture=neutral, PublicKeyToken=null' was not found. Please review the project's references. (MT3005)

Using Fusillade with async / await with PCL Profile7 for Xamarin.IOS host crashes app

First of all thanks for such a nice package!

I'm experiencing some weird behavior using Fusillade with async / await with PCL Profile7 for Xamarin.IOS host crashes the app, here is the callstack:

I tried with many other PCL profiles - same result. I tried avoid async / await - and it was successfully working using just httpClient.PostAsync.Result - but I want to avoid it in our solution.
I tried to avoid using PCL library by using just Xamarin.IOS without PCL shared project - and it was working successfully, though in some logs from our beta we received async / await app crashes - but I cannot tell if Fusillade was the cause.

Tried to use HttpClient without Fusillade with all mentioned-above cases - working like charm.
I know it could be some weird PCL mambo-jambo - but still I think it is helpful to letting you know.

Looking forward for a fix
Thanks!

Fusillade install failed due to Rx-Interfaces

Hi,

I have tried to install Fusillade on a PCL (.NetPortable4.5), but it fails when installing dependency Rx-Interfaces 2.2.4.

Tried multiple profiles: 7, 11, 259

Failure report:
Error Could not install package 'Rx-Interfaces 2.2.4'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile259', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. 0

[Bug]: Azure Blob image URL will throw an exception when there are invalid values

Describe the bug 🐞

A bug happened!

Azure Blob image URL will throw an exception when there are invalid values

https://github.com/reactiveui/Fusillade/blob/2.4.67/src/Fusillade/RateLimitedHttpMessageHandler.cs#L176-L180

Changing here should fix this issue
Use HttpHeaders.TryAddWithoutValidation Method

https://blob.steampp.net:443/jpeg/deb006f3186f2bf5c905f8e55f3d35e7bf24319a2f2143ab4cafffc5fcc00f817e30bd6d2c3a580d4423755f4f8f08f2.jpg

Step to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Reproduction repository

https://github.com/reactiveui/ReactiveUI

Expected behavior

This should happen...

Screenshots 🖼️

No response

IDE

No response

Operating system

No response

Version

No response

Device

No response

ReactiveUI Version

No response

Additional information ℹ️

No response

Differing requests can be returned the same deduplicated response

It's possible that some differing requests receive the same response.

For example, making requests to the same endpoint, but with a different If-Modified-Since header, can result in the second request receiving the response from the first. These requests are perhaps being deduplicated when they should not be.

Our application makes use of the If-Modified-Since and If-None-Match headers. Looking at the UniqueKeyForRequest method, it appears that these headers are not taken into consideration. It also appears that non-idempotent requests such as POSTs may also be deduplicated, when a client may expect all of these requests to be send and responded to individually as state changes on the server.

Does this assessment seem on the right track, and would you accept a PR for these changes? Thanks!

Update NuGet Package

The NuGet available on nuget.org does not include the critical #15 fix. Can someone update it? @paulcbetts? Thanks.

Refit + Fusillade fails with System.ObjectDisposedException: Cannot access a disposed objec

I have a xamarin forms project. I hoped to use both Refit and Fusillade for it.
When i use either of them everything works fine but when i start to use them together then requests fails.

Fusillade 1.0.0
Xamarin.Forms 3.0.0.296286
Refit 4.3.0

**Single ** request works fine. Fails only when Fusillade deduplicates queries.

The code is simple. I got an empty ContentPage with button and label.
The button click handler contains code:

var api = RestService.For<IScheduleApi>(
	new HttpClient( NetCache.UserInitiated )
	{
		BaseAddress = new Uri( Config.ApiUrl )
	} );
			
var result = await api.GetText();
this.TextLabel.Text = result;

IScheduleApi is the following:

[Headers("Accept: application/json")]
    public interface IScheduleApi
	{
		[Get("/schedule")]
		Task<string> GetText();
	}

The web service just sleeps and returns text:

Thread.Sleep(4000);
return "Text";

When i click on button and wait then i get the response and everything is fine.
When i click next time and again wait - everything works.
But if i do more that one click then i get the exeption. Though i am not sure which one of the libraries causes it

04-03 19:18:50.144 I/MonoDroid(10742): UNHANDLED EXCEPTION:
04-03 19:18:50.174 I/MonoDroid(10742): System.ObjectDisposedException: Cannot access a disposed object.
04-03 19:18:50.174 I/MonoDroid(10742): Object name: 'System.Net.Http.StreamContent'.
04-03 19:18:50.174 I/MonoDroid(10742): at System.Net.Http.HttpContent+d__18.MoveNext () [0x00027] in :0
04-03 19:18:50.174 I/MonoDroid(10742): --- End of stack trace from previous location where exception was thrown ---
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <fcbf47a04b2e4d90beafbae627e1fca4>:0 04-03 19:18:50.174 I/MonoDroid(10742): at Refit.RequestBuilderImplementation+<>c__DisplayClass11_01+<b__0>d[T].MoveNext () [0x003d2] in :0
04-03 19:18:50.174 I/MonoDroid(10742): --- End of stack trace from previous location where exception was thrown ---
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at TempStaff.SchedulePage+d__3.MoveNext () [0x00051] in D:\Code\Avilum\tempstaff\TempStaff\TempStaff\SchedulePage.xaml.cs:69
04-03 19:18:50.174 I/MonoDroid(10742): --- End of stack trace from previous location where exception was thrown ---
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__6_0 (System.Object state) [0x00000] in :0
04-03 19:18:50.174 I/MonoDroid(10742): at Android.App.SyncContext+<>c__DisplayClass2_0.b__0 () [0x00000] in <551e90b840814b76a3d15b7bbaa8a77c>:0
04-03 19:18:50.174 I/MonoDroid(10742): at Java.Lang.Thread+RunnableImplementor.Run () [0x00008] in <551e90b840814b76a3d15b7bbaa8a77c>:0
04-03 19:18:50.174 I/MonoDroid(10742): at Java.Lang.IRunnableInvoker.n_Run (System.IntPtr jnienv, System.IntPtr native__this) [0x00008] in <551e90b840814b76a3d15b7bbaa8a77c>:0
04-03 19:18:50.174 I/MonoDroid(10742): at (wrapper dynamic-method) System.Object.aa6e990f-8152-4823-ae62-44e7a273b201(intptr,intptr)

An exception was thrown by the type initializer for Fusillade.NetCache

So I migrated to the Xamarin.iOS unified-API, and all works fine on an iOS simulator, when I try to run on my iPhone 5S, it crashes on startup with no exceptions thrown.

All I get is a message in the application output window "An exception was thrown by the type initializer for Fusillade.NetCache".

ModernHttpClient + PortableRest

Hi,

I noticed that Fusillade version 0.6 doesn't work with ModernHttpClient + PortableRest (Xamarin.Forms project), but adding the reference directly to Fusillade code works. Could you generate a new version for Fusillade since the latest one is from 2014?

Thanks,

How to use Fusillade without ModernHttpClient in Xamarin Forms?

Hi!
Considering that Stackoverflow does not have a tag for Fusillade, I'm not sure if I would get an answer there. I hope this is the right forum for this question, if not please excuse.

As per this article, I would deduce that the use of ModernHttpClient within a XF project would be redundant. Would you be able to guide me on how I could use Fusillade (with Refit) without ModernHttpClient?

Thanks in advance.