Today I sent the version, and found an anomaly online, all from the unified model, Juchang system 8.0. After a moment’s thought, only MATE -10 was found, because the testing machine was limited, we could only borrow the boss’s personal machine to do the test. Sure enough, a steady reappearance.
The problem is that WXEntryActivity, which is commonly used when we do development, needs to call the wechat interface (social login, payment) to activate the activity. For example, I access the SDK of a third party to log in to wechat, then activate the activity, and then press Back. The APP flashes back.
I haven’t tested the payout yet, and I expect it to be the same.
So did this guy on Google https://stackoverflow.com/questions/47093127/facebook-android-only-fullscreen-opaque-activities-can-request-orientation This bug occurs when calling Facebook’s interface
Follow the friend’s answer
http://www.codeprocedures.com/question/lock-screen-orientation-when-targeting-android-api-27-with-a-nonopaque-activity/
Temporary solution 1 # # # remove WXEntryActivity android: screenOrientation = “portrait”
But what if you can’t change the list? For example, some third-party SDK calls are written in jar packages ### Temporary fix version 2 reduced to 26
## Cause: My project compileSdkVersion and targetSdkVersion have both been raised to 27.
reference https://stackoverflow.com/questions/46992843/interstitial-admob-ads-illegalstateexception-only-fullscreen-activities-can -r
# # subsequent’s issue tracker is https://issuetracker.google.com/issues/68454482