You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
android: the released APK declares no INTERNET permission, so joining an incident cannot work #381
src/LageBuch.App.Android/AndroidManifest.xml declares no <uses-permission android:name="android.permission.INTERNET" />, and nothing in LageBuch.App.Android.csproj adds one.
.NET for Android injects INTERNET automatically only for Debug builds (for the debugger). The local debug output confirms the injection:
android.permission.DUMP comes from androidx.profileinstaller's benchmark receiver. There is no INTERNET string anywhere in the manifest's string pool.
Impact
Without INTERNET, Android refuses every socket the app opens. The Android companion's entire purpose is joining an incident hosted on a laptop over LAN/Tailscale (RemoteIncidentSession, https://<host>:5859), so on a release build that must fail — the app can only ever work against a debug deployment.
This should be confirmed on a real device against a release APK before assuming the scope; it is possible something else masks it. But relying on a Debug-only auto-injection is wrong regardless of the outcome.
Fix
Declare it explicitly in src/LageBuch.App.Android/AndroidManifest.xml:
Worth adding alongside: a check that the release APK carries the expected permission set, so this cannot regress silently. The manifest is also the right place to keep android:usesCleartextTraffic="false" company — the app is TLS-only by design.
Found via
Verifying claims for docs/datenschutz-und-sicherheit.md (#380). The data-protection page deliberately makes no claim about Android network permissions until this is resolved.
Activity
docs: 0.6.0 als veröffentlicht führen (#450)