Barry
More than one avatar was detected! There might be multiple accounts sharing this same name.
Assigned
No issues.
Reported
Comments
Chunk loading is still not great. I'm still hitting void walls flying around, even with the vastly reduced max render distance.
I'm getting the same crash with 1.16.40 on android 8.0 whenever trying to sign in, either from the home screen or profile settings.
I captured this from the adb logcat at the time:
09-19 17:15:01.214 7706 7706 D AndroidRuntime: Shutting down VM
09-19 17:15:01.214 7706 7706 E AndroidRuntime: FATAL EXCEPTION: main
09-19 17:15:01.214 7706 7706 E AndroidRuntime: Process: com.mojang.minecraftpe, PID: 7706
09-19 17:15:01.214 7706 7706 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.mojang.minecraftpe/com.microsoft.xal.browser.WebView}: java.lang.IllegalStateException: Only fullscreen opaque activities can request orientation
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3303)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3411)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.ActivityThread.-wrap12(Unknown Source:0)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1994)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:108)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.os.Looper.loop(Looper.java:166)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7529)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Only fullscreen opaque activities can request orientation
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.Activity.onCreate(Activity.java:1081)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at com.microsoft.xal.browser.WebView.onCreate(WebView.java:150)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7383)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1218)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3256)
09-19 17:15:01.214 7706 7706 E AndroidRuntime: ... 9 more
09-19 17:15:01.217 1203 2851 W ActivityManager: Force finishing activity com.mojang.minecraftpe/com.microsoft.xal.browser.WebView
09-19 17:15:01.220 1203 2851 W ActivityManager: Force finishing activity com.mojang.minecraftpe/.MainActivity
09-19 17:15:01.221 1203 2851 V WindowManager: findFocusedWindow: AppWindowToken{eb1fe42 token=Token{6c98c8d ActivityRecord{5e68924 u0 com.mojang.minecraftpe/.MainActivity t5}}} below Reached focused app=AppWindowToken{31d4195 token=Token{ce34d4c ActivityRecord{e05e97f u0 com.mojang.minecraftpe/com.microsoft.xal.browser.WebView t5}}}
I notice this behavior has manifested for different users at different times and in different versions. I didn't see it until 1.19.31 and even then it wasn't until a few days after the update. Could this be related to a console setting or update and not exclusively a game update?