As in my post from 12 days ago, I am unable to run the app on API 26 or greater (runs fine from API 16 - 25).
I can see a report from Sept 2017 of a similar issue that was resolved - I see no other issues regarding Android 8 compatibility.
Environment: Fuse 1.9
Device: Sony Xperia XZ1 Compact API level 26
I would appreciate some response on this as this is holding everything up.
Here is the error output when I try to run the app:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.oskk.hoteloxy/com.oskk.hoteloxy.hoteloxy}: java.lang.IllegalStateException: Only fullscreen opaque activities can request orientation
FATAL EXCEPTION: main
Process: com.oskk.hoteloxy, PID: 10005
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.oskk.hoteloxy/com.oskk.hoteloxy.hoteloxy}: java.lang.IllegalStateException: Only fullscreen opaque activities can request orientation
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2817)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2892)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1593)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6541)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
Caused by: java.lang.IllegalStateException: Only fullscreen opaque activities can request orientation
at android.app.Activity.onCreate(Activity.java:986)
at android.support.v4.app.BaseFragmentActivityDonut.onCreate(BaseFragmentActivityDonut.java:39)
at android.support.v4.app.FragmentActivity.onCreate(FragmentActivity.java:297)
at android.support.v7.app.AppCompatActivity.onCreate(AppCompatActivity.java:85)
at com.oskk.hoteloxy.hoteloxy.onCreate(hoteloxy.java:53)
at android.app.Activity.performCreate(Activity.java:6975)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1213)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2770)
… 9 more
I tested a API 26 targeted version with Android 8.1 and it worked, so I forgot about this issue, but I wonder if the problem still persists on Android 8.0?
Yes, indeed. The app does run on API 27 and 28. It is just API 26 that fails (my original post stated that it fails on 26 and above which is incorrect).
This fails on 26, works on 27 & 28 (Pixel 2, Firebase test lab):
Hello! I didn’t have time to look into the issue in depth so I forgot about it. I guess (and hope) a lot of users have the chance to update from 8.0 to 8.1 and skip this issue. There are a lot of suggestions to tackle this internally, but I’m waiting for an update to the Fuselibs, since I don’t have the opportunity to test this in API 26.
@acoad@Matti_Tihverainen Have you guys tried to isolate the module that’s causing the issue? Is it a 3rd party module that’s breaking that needs an update? Does a “vanilla app” run on 26?
I see. It’s the older build tools that is the issue. I don’t think that is a problem for me.
Here are my current settings. Will your solution work for this?
Fuse 1.9: After fresh install, and NDK16b replacement, I’m able to build and run with these settings which I tested on a low Marshmallow(23), a mid Marshmallow(23) and a low Oreo(26):
With latest Uno: had to replace with NDK16b, can only build with latest tools as it statically uses latest Gradle(4.4), my results with settings used above: low Marshmallow(23) - Built + crash, a mid Marshmallow(23) - Built + run and a low Oreo(26) - Built + run
A low Marshmallow (Android 6 or API 23) is about a $35 device (its on the low end of the device spectrum) and a mid Marshmallow is about a $200 device, they’re both running Marshmallow.
The main difference is the hardware; the low end device can only install like a handful of apps, has a 3.5" display, 1.2Ghz Quad-Core, 512MB RAM, 2MP rear cam, 0.3MP front cam, 8GB onboard, 3G and 1400mAh battery (very popular device though). It crashed upon launch with the latest Uno. Not sure what’s causing it to crash as its on the same OS version as the mid and works fine on the current Fuse 1.9.
The mid hardware is a 5.1" display, 2.5Ghz Quad-core, 16MP rear cam, 2MP front cam, 16GB onboard, LTE and 2800mAh battery.
OK. I understand. I don’t think users of this app will be running $35 or thereabouts devices so I should probably move ahead and set up a new environment per your prior instructions.
Do you plan to do any further work on this issue or are you done?