sure, send me an iphone or ipad and i'll sign right up 
what a strange beta process, but that seems to be on apple. you should be able to reproduce then verify the issue is fixed on your side. if you aren't able to reproduce it, then maybe something extremely odd is going on here with metadata, old db schema... i don't know your architecture. we can maybe talk further if that is the case. the patch note to me implies it was reproduced and corrected, as i'd never push a commit or accept a PR that was taking a blind shot without reproduction in this context. especially since this pip seems so finicky.
just let me know if you weren't able to actually reproduce it in your own testing. i'm not sure if the "seen it personally" implies that, or in your historical personal usage of channels.
and btw, i'm a salaried senior software engineer. you've either reproduced it and fixed it, or not. i feel i've already went above and beyond as i've reported a handful of pretty glaring bugs over the years, and typically get the response like i do in this thread. "oh that can't possibly be happening" until i prove it. i get you typically provide support for people who don't understand software, but it's still annoying.
this isn't a piece of open source software i setup and maintain myself, helping an open source maintainer. i understand you're a small outfit and probably have other gigs, but i have to draw the line on providing free testing to paid products, and that's my personal choice. i can't even jump through the hoops anyway.
but once again, i don't have another apple device and i'm not even at home this weekend, and i doubt my wife would be willing to give this a shot 