Bruno Prieto Reis

My solution was: remove the Procfile.... symfony will detect the heroki deploy and create it. this is what was created: ``` web: heroku-php-apache2 web ```

Well, I see it's on app.json, but for some reason it was not loaded. Now it's complaining about "secret"

It worked for me using the app.json and changing the config.yml to: ``` secret: '%env(SYMFONY__SECRET)%' ```` Maybe you did it too, but it's not in the docs.

in composer.json... ``` ... "autoload-dev": { "psr-4": { "Tests\\": "tests/" } }, "minimum-stability": "dev", "require": { ... ```

Please notice that if you are using tape-watch with @babel/register the line should start with: `tape-watch -r @babel/register ...` Kind of obvious when you know it, but took me a...

Hey @colinskow, sorry, I don't understand your answer. If something is added to the live query, I understand it's already on Pouch. Please clarify. My main concern here is how...

The error is "console.error: "(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit."

It seems that you just postponed the message because when you call: ``` db._changeListener .on('change', changeHandler) .on('error', errorHandler); ``` it's throwing that error on the _changeListener now. I'm not sure...

Not sure if this is exactly what you want, but you can test this code on localhost by acquiring consent on the login: ```

This seemed to be happening due to the wrong "Allowed Web Origins". I'm adding it here to facilitate the reproduction, but the message is still very confusing, so I keep...