Without enabling all permissions., ARSetup( ) will put the AppGameKit Player into the Background 1:5 Broadcasts; with all Permissions Enabled (manually via App Settings) it will ALWAYS push the App into the Background when connected and broadcasting.
Exporting as an APK., and all permissions are disabled by Default.
I think it's silly we have to manually add Check and Request (and we can't even find out IF Permission was granted without Checking again... why doesn't Request Permission have a Return?)
In any case., enabling Camera access (which is needed for ARCore) produces the same behaviour as the AppGameKit Player; where it doesn't close / crash the App, it just instantly pushes it into the Background.
Now as a note:
The APK is using Android API 31 (most current AppGameKit allows)., I've enabled everything in the APK Export and made ARCore a Requirement.
I'm trying to run this on a Nokia 5.4 with Android 12 and ARCore is installed, updated and supported just fine in other Apps.
As a note., the AppGameKit Player is still present within Built Applications; but a minor difference is customisable elements are prescribed in the App Store version; so you can't change the Renderer for example, or AdMod links to a tgc defined website that doesn't exist.
Stuff like that, which would be written to the APK/App on Build.
I'm familiar with this App behaviour from when I had an iPod Touch., as when Apps used to do this; it meant that I had to upgrade iOS (then Apple being the "Consumer Friendly" Company they are; stopped supporting my device, as forcing people to pay another £400 for a new Device is easier than supporting additional older hardware... but they also stopped developed from having older versions of the Apps, i.e. they HAD to be using a "Supported" version of iOS to build their Apps for the Store and stay on there.
It's not like Google who just hides them from the Store, but can be accessed via a manual link.
Anyway, as noted... this is behaviour common to "Incompatible API" versions, because gods knows it's obviously impossible to create a pop-up that says "This App is no longer Compatible with your Device" ... no, let's just let it run and keep minimising because it can't run and have the User confused as **** as to what is going on. That's a MUCH better solution, obviously.
(That's not a dig at TGC, but at the laziness of Apple and Google...)
Still it seems like the Feature for the moment is unavailable.