we've seen this from time to time with ios and safari, did a major change to fix it awhile ago that mostly worked, but out of the blue someone will report it and we haven't been able to consistently reproduce it to figure out why, so I apologize for digging on details
safari and ios are linked that should be good enough for test in an emulator, thanks for the info... may ping you to try again... reimbursing your sats ++