Repository navigation
Conversation
… Android The paywall is the SDK's own Activity, so a host app that runs full-screen (immersive) gets the status and navigation bars back the moment a paywall opens. superwall-android's edge-to-edge handling then pads only the bottom system-bar inset; in landscape the 3-button navigation bar sits on a side and covers paywall content there. The new option is bridge-level (no native counterpart): when true, the Android bridge registers ActivityLifecycleCallbacks once at configure and, whenever SuperwallPaywallActivity is created or resumed, hides the system bars with the sticky-immersive behaviour (a swipe from the edge shows them transiently). The activity is matched by class name so an upstream rename degrades to a no-op. Default false; ignored on iOS. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The paywall is the SDK's own Activity, so a host app that runs full-screen (immersive) gets the status and
navigation bars back the moment a paywall opens. superwall-android's edge-to-edge handling then pads only the
bottom system-bar inset; in landscape the 3-button navigation bar sits on a side and covers paywall content.
Change
A new bridge-level option,
PaywallOptions.HideAndroidSystemBars(defaultfalse, ignored on iOS). Whentrue, the Android bridge registers
ActivityLifecycleCallbacksonce at configure and, wheneverSuperwallPaywallActivityis created or resumed, hides the system bars with the sticky-immersive behaviour(a swipe from the edge shows them transiently). The activity is matched by class name so an upstream rename
degrades to a no-op. No native SDK change is required.
Verification
Moto G24 Power (Android, 3-button navigation), landscape app: with the option on, the paywall opens without
bars and content is no longer covered on the side. Off, behaviour is unchanged.
Open question for maintainers: the side-inset padding in landscape looks like a superwall-android issue
independent of this option; happy to file it separately.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LTHPGB4qyAwDVYmQHW87ex