Maurice McCabe

This is likely a git set-up issue and not related to fledge: https://stackoverflow.com/questions/43842239/unknown-revision-or-path-not-in-the-the-working-tree-error-for-first-push-to-emp Let me know if you continue having a problem with running 'fledge beta' after resolving any git...

A little context that might help resolve this issue: Before starting a beta, as a precaution, fledge runs some checks on the local dev branch. This is important because the...

One way to confirm everything is as anticipated when using fledge, is to fork the repo fledge uses for a demo app and run a beta release on it: https://github.com/mmcc007/todo...

I looked at the build in travis of your fork: https://github.com/v2Nitesh/todo and found only one build: https://travis-ci.org/v2Nitesh/todo/builds/523436073 This is a release build. I expected to find a beta build similar...

Great!... looks like the beta build is being triggered. Both jobs are generating errors related to signing So each job requires signing to be setup. Not an easy thing to...

@niranjan-b-prajapati you can test locally for android using ``` cd android fastlane beta ``` and for ios ``` cd ios fastlane beta ```

There's a script for that: ``` scripts/ci.sh --get ```

Well, I suppose it was not anticipated it would come up... but now that you mention it.. it should probably be in there.

@Joematpal The link above is no longer working. Were you able to resolve this? If so please close this issue. Otherwise feel free to add to this issue.

Here is an example of using Aqueduct server and a dart client to implement a chat room using sockets: https://github.com/stablekernel/aqueduct_examples/tree/master/cli_chat_websockets Can probably adapt this to the `todos_repository_simple` or your app....