11---
22title : Stricter Android `Intent` Verification for App Entrypoints
3- description : >
3+ description : >-
44 Android `Intent` extras for routing, entrypoints, and cached engines
55 are now strictly verified.
66---
@@ -57,7 +57,7 @@ This exposed applications to security vulnerabilities, including:
5757 (via ` EXTRA_CACHED_ENGINE_ID ` and ` EXTRA_CACHED_ENGINE_GROUP_ID ` )
5858 to access user-restricted states.
5959
60- To mitigate these issues, we introduced a strict verification check using
60+ To mitigate these issues, Flutter introduced a strict verification check using
6161Android's ` getLaunchedFromUid() ` (on Android 14+)
6262and ` getCallingPackage() ` (on Android 13 and below).
6363
@@ -99,7 +99,7 @@ will no longer have an effect in release builds.
9999* ** Internal Cached Engine & Entrypoint Launches:**
100100 If an application launches a pre-warmed cached engine
101101 or custom entrypoint dynamically from its own native code
102- (e.g. from a background [ ` Service ` ] [ ] or [ ` BroadcastReceiver ` ] [ ]
102+ (for example, from a background [ ` Service ` ] [ ] or [ ` BroadcastReceiver ` ] [ ]
103103 using standard ` startActivity(intent) ` ),
104104 it will fail to resolve the cached engine or entrypoint parameters
105105 on Android 13 and below if the target activity is exported.
@@ -111,7 +111,7 @@ You are **NOT affected** and do not need to migrate
111111if ** ANY** of the following are true:
112112- ** You do not use custom intent extras:** You only use the default
113113 entrypoint (` main() ` ) and route (` / ` ), and do not launch cached engines
114- (i.e. , you never pass ` route ` , ` dart_entrypoint ` , ` dart_entrypoint_args ` ,
114+ (that is , you never pass ` route ` , ` dart_entrypoint ` , ` dart_entrypoint_args ` ,
115115 ` cached_engine_id ` , or ` cached_engine_group_id ` as ` Intent ` extras).
116116- ** Your activity is internal:** Your target ` FlutterActivity ` or
117117 ` FlutterFragmentActivity ` is non-exported (` android:exported="false" ` ).
@@ -123,7 +123,7 @@ Depending on your application's use case,
123123you should migrate using one of the following methods:
124124
125125### For Push Notifications, App Shortcuts, and Home Screen Widgets
126- We recommend migrating to use standard [ deep links] [ ]
126+ Migrate to standard [ deep links] [ ]
127127instead of ` Intent ` extras.
128128
129129** Before (Insecure):**
@@ -219,7 +219,7 @@ In your `AndroidManifest.xml`:
219219
220220#### Option 4: Subclass and programmatically define parameters
221221For dynamic configurations that cannot use ` startActivityForResult `
222- (e.g. launches from background ` Services ` or ` BroadcastReceivers ` ),
222+ (for example, launches from background ` Services ` or ` BroadcastReceivers ` ),
223223you can subclass ` FlutterActivity ` or ` FlutterFragmentActivity `
224224and programmatically supply the parameters:
225225
0 commit comments