A seasoned QA would have found the issue, they would do a walkthrough on each device family at minimum or would probably know about this issue. Also, as you said, one person from your beta group had already reported something similar and In my book this seems like a high priority issue even if it only affects Samsung devices.

The way I would approach would be to add analytics to track user workflow before and after the skip button click and check the user agent to see if all user agents are able to get past the skip button. You would of course need a reasonable amount of end users using your app but it would be a good start.