AppSupport Galaxy Wearable white screen

Bug Reports
1

REPRODUCIBILITY: 100%
OS VERSION: 5.0.0.68
HARDWARE: xperia 10 III
UI LANGUAGE: Finnish
REGRESSION:

DESCRIPTION:

Now when it’s possible to use Bluetooth in AppSupport, I tried to pair a Samsung Watch7. Bluetooth works but when trying to launch Galaxy Wearable app there is only a white screen. Looking at logcat I think the reason is this:
AndroidRuntime: java.lang.RuntimeException: Unable to create application com.samsung.android.waterplugin.WaterPluginApplication: java.lang.NullPointerException: null cannot be cast to non-null type android.net.wifi.p2p.WifiP2pManager

Any ideas? pm list features does not show android.hardware.wifi.direct or similar.

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. launch Galaxy Wearable

EXPECTED RESULT:

Application launches

ACTUAL RESULT:

White screen

MODIFICATIONS:

ADDITIONAL INFORMATION:

2

Whitescreen in android apps usually points to problems due to missing google services

3

WiFi(-management) is one of those things that are not plumbed in to AAS. If the app refuses to start without it, it is quite poorly made.

4

Good thing too. We really really don’t want it to have access to configuring any networks.

5

Respectfully disagree, I would like AppSupport to be able to change my active WiFi network. My usecase is using Canon’s Camera Connect app: It first negotiates / connects over Bluetooth before upgrading to a WiFi connection (phone connects to camera) for a lower latency, higher throughput connection. This is especially useful for the “remote live view shooting” function since unlike Android devices, AppSupport doesn’t seem to make available the camera when connected via USB-C (which enables using the app on the phone as a real-time monitor).

Regardless, an app failing to even open when it can’t get WiFi / incorrectly casts to non-nullables (so a developer assumption) is pretty ridiculous.