Maurice McCabe

@miquelbeltran I took a very similar approach some time ago that seemed to work when learning redux (wasn't familiar with epics or other approaches at the time). I created a...

I ended-up moving to bloc arch. The latest is provider arch. Both have been endorsed/promoted by Flutter Team (as well as redux). https://www.youtube.com/watch?v=d_m5csmrf7I&t=9s

There's a temporary check for this during the build: https://github.com/brianegan/flutter_architecture_samples/blob/master/scripts/runTests.sh#L32 and https://github.com/brianegan/flutter_architecture_samples/blob/master/scripts/ci.sh#L36 The existing generated files still work. But yes, should be fixed. BTW: looks like I have a fix...

@zacps Should be ignoring any physical devices not specified in config file. Looks like flutter daemon is having a problem starting the emulator. Try running with the -v option and...

Try running with the -v option and provide config file

@flutterfromscratch provide output of ``` flutter doctor -v cat screenshots.yaml screenshots -v ```

There is no support for a device named 'Pixel_2_API_26' in [screens.yaml](https://github.com/mmcc007/screenshots/blob/80f5aa25919c7abe7614f5ccb8a9d9f759fc03dd/lib/resources/screens.yaml), so the screenshots cannot be framed. To add a screen for 'Pixel 2' see [README](https://github.com/mmcc007/screenshots/blob/master/test/resources/README.md).

Wait, no images were generated?

It may be due to a recent refactoring. I will try to reproduce it and put out a fix.

That's weird, I got your comment via email. But I don't see the comment in the issue and don't see the PR. On Thu, Dec 12, 2019 at 11:33 AM...