Thomas Adam

@Lexrijvers feel free to open a PR to add this option. Thanks!

The same issue occurred in our app after upgrading, but only once at the moment for a Samsung Galaxy A5 with Android 6.0.1

The metrics are lazy, can you confirm that you have traffic on the specified NSQ nodes?

I have implemented this for a long time for sharding: see #325 generally it makes the same what you explain here, but it's incomplete and need some rewrites to fit...

Hey. the first thing you need is my fork of the JMSSerializerBundle, you found this here: https://github.com/tecbot/JMSSerializerBundle then define class mappings in the config: ``` tecbot_amf: use_serialization: true # activate...

You need to serialize the entity before you return. ``` namespace My\ExampleBundle\Amf; use Symfony\Component\DependencyInjection\ContainerAware; class ExampleAmfService extends ContainerAware { public function getByIdAction($id) { $entity = $this->container->get('my.example_bundle.example_service')->getById($id); return $this->container->get('serializer')->serialize($entity, 'vo'); }...

I already referenced the misleading code lines. Creating a v1 pubsub trigger will cause the issue always: ```ts import { onInit } from 'firebase-functions' import * as functions from 'firebase-functions/v1'...