Indeed. Unfortunately, with resources being spread as thin as they are over mesh–and the app receiving reasonably frequent updates for Mesh, it can sometime prove difficult to determine where the issue originated. Further adding in that Samsung tends to delay the release of newer Android versions a bit and some phones are likely seeing newer updates, there’s nothing discounting that they may not be introduced in these new versions.
I have a few old Note 4s on Android 5 lying around that never seemed to experience this issue, so I suspect it could be something that’s more recent in the Android ecosystem.
Needless to say, as it is an ongoing and concerning problem that’s impacting our community, we are addressing it. It may require our mobile team getting a few more Samsung devices in the hands to really nail down this issue
In the meantime, for anyone who is having this issue, if they have a non Samsung device available, the process should still go through fine. If that isn’t an option, there is always the CLI as a plan B.