LoRa App Server object doesn`t exist when click on device

Im running lora-gateway-bridge, loraserver and lora-app-server version 3.2.0 on CentOS. I have created multiple network servers, all necessary databases, configuration files. The problem is that no matter which network server is used, when Im trying to add my OTAA device (device is fine - everything works on my raspberry pi server), after I have added devEUI, application key, activation is not working and every time I open this added device from the list in application, pop up error appears “object does not exists” and in lora-app-server log I see this:
Oct 01 13:49:29 my.domain lora-app-server[1349]: time=“2019-10-01T13:49:29+03:00” level=info msg=“finished unary call with code NotFound” error=“rpc error: code = NotFound desc = object does not exist” grpc.code=NotFound grpc.method=List grpc.service=api.DeviceQueueService grpc.start_time=“2019-10-01T13:49:29+03:00” grpc.time_ms=4.611 peer.address="[::1]:33382" span.kind=server system=grpc
What could be causing this? I see that device menu page looks different from my raspberry pi server (unfortunately I have forgot the version I have there).

Fixed in the latest app server point release. It was an errant error message that just meant the device hadn’t joined yet.

Latest test version or stable? When I was using version 3.3.1 for all services, I had similar error when adding gateway. In that case gateways weren’t added at all.

See Bugfixes.