|
|
|
@ -5,48 +5,47 @@
|
|
|
|
|
In most cases you can leave this as-is, but you if you want to provide
|
|
|
|
|
additional functionality it is fine to subclass or reimplement
|
|
|
|
|
FlutterApplication and put your custom class here. -->
|
|
|
|
|
<uses-permission android:name="android.permission.INTERNET"/>
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
|
|
|
|
|
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>
|
|
|
|
|
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
|
|
|
|
|
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
|
|
|
|
|
<uses-permission android:name="android.permission.INTERNET" />
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
|
|
|
|
|
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
|
|
|
|
|
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
|
|
|
|
|
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
|
|
|
|
|
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
|
|
|
|
|
|
|
|
|
|
<application
|
|
|
|
|
android:name="${applicationName}"
|
|
|
|
|
android:label="amap_map_example"
|
|
|
|
|
android:icon="@mipmap/ic_launcher">
|
|
|
|
|
android:icon="@mipmap/ic_launcher"
|
|
|
|
|
android:label="amap_map_example">
|
|
|
|
|
<!-- <meta-data
|
|
|
|
|
android:name="com.amap.api.v2.apikey"
|
|
|
|
|
android:value="900f72eeee0f21e435cebb0ef155582a" /> -->
|
|
|
|
|
<activity
|
|
|
|
|
android:name=".MainActivity"
|
|
|
|
|
android:launchMode="singleTop"
|
|
|
|
|
android:theme="@style/LaunchTheme"
|
|
|
|
|
android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
|
|
|
|
|
android:hardwareAccelerated="true"
|
|
|
|
|
android:launchMode="singleTop"
|
|
|
|
|
android:theme="@style/LaunchTheme"
|
|
|
|
|
android:windowSoftInputMode="adjustResize">
|
|
|
|
|
<!-- Specifies an Android theme to apply to this Activity as soon as
|
|
|
|
|
the Android process has started. This theme is visible to the user
|
|
|
|
|
while the Flutter UI initializes. After that, this theme continues
|
|
|
|
|
to determine the Window background behind the Flutter UI. -->
|
|
|
|
|
<meta-data
|
|
|
|
|
android:name="io.flutter.embedding.android.NormalTheme"
|
|
|
|
|
android:resource="@style/NormalTheme"
|
|
|
|
|
/>
|
|
|
|
|
android:name="io.flutter.embedding.android.NormalTheme"
|
|
|
|
|
android:resource="@style/NormalTheme" />
|
|
|
|
|
<!-- Displays an Android View that continues showing the launch screen
|
|
|
|
|
Drawable until Flutter paints its first frame, then this splash
|
|
|
|
|
screen fades out. A splash screen is useful to avoid any visual
|
|
|
|
|
gap between the end of Android's launch screen and the painting of
|
|
|
|
|
Flutter's first frame. -->
|
|
|
|
|
<meta-data
|
|
|
|
|
android:name="io.flutter.embedding.android.SplashScreenDrawable"
|
|
|
|
|
android:resource="@drawable/launch_background"
|
|
|
|
|
/>
|
|
|
|
|
android:name="io.flutter.embedding.android.SplashScreenDrawable"
|
|
|
|
|
android:resource="@drawable/launch_background" />
|
|
|
|
|
<intent-filter>
|
|
|
|
|
<action android:name="android.intent.action.MAIN"/>
|
|
|
|
|
<category android:name="android.intent.category.LAUNCHER"/>
|
|
|
|
|
<action android:name="android.intent.action.MAIN" />
|
|
|
|
|
<category android:name="android.intent.category.LAUNCHER" />
|
|
|
|
|
</intent-filter>
|
|
|
|
|
</activity>
|
|
|
|
|
<!-- Don't delete the meta-data below.
|
|
|
|
|