Server crashing on Google Refund Scheduler calls

Server panic caused by incorrect UUID length 0 in string “”

  1. Versions: Nakama 3.19, Linux binary
  2. Server Framework Runtime language: Go
panic: uuid: incorrect UUID length 0 in string ""
Jan 06 06:11:55 ip-172-31-4-221.ap-south-1.compute.internal nakama[11418]: goroutine 127 [running]:
Jan 06 06:11:55 ip-172-31-4-221.ap-south-1.compute.internal nakama[11418]: github.com/gofrs/uuid/v5.Must(...)
Jan 06 06:11:55 ip-172-31-4-221.ap-south-1.compute.internal nakama[11418]: github.com/gofrs/uuid/v5@v5.0.0/uuid.go:282
Jan 06 06:11:55 ip-172-31-4-221.ap-south-1.compute.internal nakama[11418]: github.com/heroiclabs/nakama/v3/server.(*LocalGoogleRefundScheduler).Start.func1()
Jan 06 06:11:55 ip-172-31-4-221.ap-south-1.compute.internal nakama[11418]: github.com/heroiclabs/nakama/v3/server/google_refund_scheduler.go:122 +0x1f9c
Jan 06 06:11:55 ip-172-31-4-221.ap-south-1.compute.internal nakama[11418]: created by github.com/heroiclabs/nakama/v3/server.(*LocalGoogleRefundScheduler).Start in goroutine 1
Jan 06 06:11:55 ip-172-31-4-221.ap-south-1.compute.internal nakama[11418]: github.com/heroiclabs/nakama/v3/server/google_refund_scheduler.go:80 +0xfc

Hello @prateek-sirah, this looks like a bug, could you kindly open an issue in the Nakama repository please?