sync-service | StackSync 's synchronization service | Data Processing library

See my recent update at the bottom.

I'm actually running into the same problem. I don't have a complete answer but I feel like this is a clue to a partial answer.

From the link:

As far as I know, AppSync doesn't use wss://. I have tried this before, and my http connection was never "upgraded to a wss" connection. I had to POST a request to the http endpoint requesting a subscription connection, then AWS returned connection details containing a new endpoint (a wss url), a topic and a client id. Only then could I connect to the socket using using a third party library (using the URL AWS returned). I had to dig into their official sdk to find this out, and then through trial and error to get it to work.

I've confirmed w/ the GraphiQL tool that I do get a response when I POST my subscription graphql blob. I get a websocket url back along w/ some other items in JSON. I haven't figured out how to capture that response in Flutter yet but I'll update this if I find that piece as well.

From there, I believe we'd need to dynamically create the websocket from that new url and send our subscription graphql blob to that.

Absolutely, this is convoluted but it's the path I'm proceeding with for now.

UPDATE: AWS Amplify for Flutter now supports subscriptions! I am using a hybrid solution. I have flutter_graphql and artemis for mutations/queries. For subscriptions I am using amplify_api: '<1.0.0'. It was just released in the past weeks. It actually only took me a few minutes to get it working. Amplify automatically does the URL resolution and authentication for you.

Link to official docs

You'll need to generate an amplifyconfiguration.dart that is specific for your AWS endpoint and add it to your project. The AWS docs cover this and the person that setup your AWS endpoint should know exactly what you need.

Example from link:

Expected spy create to have been called is not an Error but a failed test.

This is happening because you haven't use callThrough(); on your spyOn either.

I found out what my problems were:

1. I needed to use the useClass property instead of the useValue property. useClass expects a constructor (or factory function) while the useValue property expects a simple object.
2. In the deps section you are basically overriding what values you want to pass into the constructor for the service. So, in my case, I had the 'TokenHttpService' injected but no logger, so my service threw an error when it tried to call this.logger.debug. After adding NGXLogger to the deps array the service worked flawlessly.

Here's my final providers array:

They do different things relative to async operations that were previously started. For example; calling setTimeout(...) starts an async operation.

• tick() moves time forward.
• flush() moves time to the end.

This can be better illustrated with the unit tests for those functions.

This unit test shows tick being used to move time forward in steps until all 10 timers have finished. Tick is called multiple times.

https://github.com/angular/angular/blob/master/packages/core/test/fake_async_spec.ts#L205

Thanks for providing all your code in the Plunker. I actually moved it to a Stackblitz so I could see exactly what you are seeing and watch it run. I had to stub the service, but that is pretty irrelevant since you are replacing it with a spy anyway.

I got it working by commenting out the providers line in your my-gardens.component.ts file in the @Component section:

Jest doesn't have a function named createSpyObj() like default jasmine has , please visit this link Jest createSpyObj which is a custom createSpyObj function in jest or just switch to jasmine instead

Just add the HttpModule in the imports of your testing module.

It needs to be there so that Http can be injected in your servie, but Http won't be used in your test since you spy on your service methods.