Checklist

• If applicable, unit tests
• If applicable, create follow-up issues for purchases-android and hybrids

Motivation

The initial fallback paywall was not good. This was the list of goals I gathered from the team

• Loading state is not the blurred image
• Fallback paywall looks better
• Errors are clear in debug mode
• We can literally delete the image used in the old fallback paywall (it's actually very large)

Description

This adds a new fallback paywall if the paywall can't render for configuration reasons. Some things to note:

• Accent color is inferred based on app icon image colors
• The fallback paywall will work on macOS
• One of the goals is to remove the giant background asset
• The warning paywall only shows in a debug configuration, where the actual fallback paywall will show in a release configuration

Example Images

Click to expand the list

[!NOTE]
These screen shots were from before some changes, But they are very close.

Fallback Paywall

Title	Light	Dark
iPad Sheet
iPad FullScreen
Loading State
Mac

Debug Paywall

Title	Light	Dark
iPad sheet
iPad full
Mac

TODO:

Tests to remove and/or replace:

• OtherPaywallViewTests.swift (the previews replace this — though emerge doesn't properly display the colors due to timing)
• PaywallViewLocalizationTests? -- They use the background image we want to delete
• Template4ViewTests -- They use the background image we want to delete
• Remove old snapshot test files -- There are gitignored files (I think) for the images we need to ensure we remove
• Remove the background asset… and update snapshot tests
• We need to do this on Android
• Share some of the App Icon and App name logic with Customer Center
• Localize the default paywall buttons