fix:苹果一键登录页面,深浅色
This commit is contained in:
1 parent
afee4b5aec
commit
b503cb7e6e
35 files changed
+687
-228
No files matched your search
@@ -29,11 +29,17 @@ abstract final class UmengService {
|
||||
|
||||
static Future<void> _init() async {
|
||||
await DeviceHeaderService.to.ensureInitialized();
|
||||
await UmengCommonSdk.initCommon(
|
||||
UmengConfig.androidAppKey,
|
||||
UmengConfig.iosAppKey,
|
||||
DeviceHeaderService.to.commonHeaders()['User-Channel'] ?? 'default',
|
||||
UmengConfig.androidPushSecret,
|
||||
// Keep the carrier-login launch path independent of UMeng Common's
|
||||
// network initialization. Waiting for this future is what left the login
|
||||
// overlay spinning forever in the base project; U-Verify is configured
|
||||
// immediately below by initOneKeyLoginIfAllowed, as in Yanting.
|
||||
unawaited(
|
||||
UmengCommonSdk.initCommon(
|
||||
UmengConfig.androidAppKey,
|
||||
UmengConfig.iosAppKey,
|
||||
DeviceHeaderService.to.commonHeaders()['User-Channel'] ?? 'default',
|
||||
UmengConfig.androidPushSecret,
|
||||
).catchError((Object _) {}),
|
||||
);
|
||||
_ready = true;
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user