MustardChef
[BUG] Marriott Bonvoy - splash screen then exits
Describe the bug
The Marriott Bonvoy app launches the splash screen, then closes itself shortly after. Previous versions of Marriott Bonvoy over the past 1-2 years never worked either regardless of WindowsUpdates. Other apps work fine.
Steps to reproduce the issue
Download Marriott Bonvoy from Google Play Store. Launch Marriott Bonvoy app.
Expected behaviour
App should open and function like on any Android cell phone.
Downloaded Build Of WSA
WSA_2407.40000.0.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon_Windows_10.7z
WSA_2407.40000.4.0_x64_Release-Nightly-GApps-13.0-NoAmazon_Windows_10.7z WSA_2407.40000.4.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon_Windows_10.7z WSA_2407.40000.4.0_x64_Release-Nightly-NoGApps-RemovedAmazon_Windows_10.7z
Windows build number
19045.6332
PC Specification
OS Name Microsoft Windows 10 Enterprise Version 10.0.19045 Build 19045 Processor AMD FX-8370 Eight-Core Processor, 4000 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. P1.60, 6/17/2016 SMBIOS Version 2.7 Embedded Controller Version 255.255 BIOS Mode Legacy Platform Role Desktop Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "10.0.19041.5553" Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 32.0 GB Available Physical Memory 19.7 GB Total Virtual Memory 54.0 GB Available Virtual Memory 39.8 GB Page File Space 22.0 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Running Virtualization-based security Required Security Properties Virtualization-based security Available Security Properties Base Virtualization Support Virtualization-based security Services Configured Hypervisor enforced Code Integrity Virtualization-based security Services Running Hypervisor enforced Code Integrity Windows Defender Application Control policy Enforced Windows Defender Application Control user mode policy Off Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Additional context
No response
