Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a comment explaining why this manifest is needed and that it hsould be kept in sync with the devsupport one?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, I added a comment. I kept this manifest aligned with the debug DevSupport manifest because debugOptimized still enables DevSupport/Dev Menu while using optimized native code, so debug-only DevSupport entries such as DevSettingsActivity and the legacy FPS overlay permission should remain available.

<!--
debugOptimized keeps JS debugging and DevSupport enabled while using
optimized native code. Keep this manifest in sync with the debug
DevSupport manifest so debug-only DevSupport components remain available.
-->
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>

<!--
On Android 17 (SDK 37) devices, apps that declare this must hold ACCESS_LOCAL_NETWORK
to reach the dev server over the local network. Loopback via `adb reverse` is exempt.
-->
<uses-permission android:name="android.permission.ACCESS_LOCAL_NETWORK"/>

<application>
<activity android:name="com.facebook.react.devsupport.DevSettingsActivity"
android:exported="false" />
</application>

</manifest>
Loading